Create a SWA integration using AIW

A SWAAn acronym for Secure Web Authentication. SWA is a SSO system developed by Okta to provide single sign-on for apps that don't support proprietary federated sign-on methods or SAML. Users can enter their credentials for these apps on their homepage. These credentials are stored such that users can access their apps without entering their credentials each time. When users first sign-in to a SWA app from their homepage, they see a pop-up message asking if they were able to sign-in successfully. integration provides Single Sign-On (SSOAn acronym for single sign-on. In a SSO system, a user logs in once to the system and can access multiple systems without being prompted to sign in for each one. Okta is a cloud-based SSO platform that allows users to enter one name and password to access multiple applications. Users can access all of their web applications, both behind the firewall and in the cloud, with a single sign in. Okta provides a seamless experience across PCs, laptops, tablets, and smartphones.) for applications that don't support proprietary federated sign-on methods. SWA works with any web-based application.

Before you begin

Task 1: Launch the Wizard

1. Verify that you are using the AdminAn abbreviation of administrator. This is the individual(s) who have access to the Okta Administrator Dashboard. They control the provisioning and deprovisioning of end users, the assigning of apps, the resetting of passwords, and the overall end user experience. Only administrators have the Administration button on the upper right side of the My Applications page. Console. If you are using the Developer Console, you need to switch over to the Admin Console. If you see < > Developer Consolein the top left corner of your console, click it, then click Classic UI to switch.
2. In the Admin Console, go to Applications > Applications.
3. Click Add Application.
4. Click Create New AppAn abbreviation of application. Essentially, it is a web-based site used to perform any number of specific tasks, and requires authentication from end users by signing in..
5. To create a SWA integration, select Web as the Platform and Secure Web AuthenticationAuthentication is distinct from authorization, which is the process of giving individuals access to system objects based on their identity. Authentication merely ensures that the individual is who he or she claims to be, but says nothing about the access rights of the individual. Authentication methods and protocols include direct auth, delegated auth, SAML, SWA, WS-Fed, and OpenID Connect. (SWA) for the Sign on method.
6. Click Create.

Task 2: Configure general app settings

The SWA App Wizard has two sections:

1. General Settings:
   • App name — Specify a name identifier for your integration.
     

     Note

     The name can only consist of UTF-8, 3 byte characters

   • App login page URL — Enter the full URL of the sign-in page for your SWA application. This URL may be different from the landing page.
   • Advanced Settings/Redirect URL — Click the Show Advanced Settings link to show the Redirect URL field. This additional field allows you to specify a redirect URL for your application.
   • Optional. App logo — Add a logo to accompany your integration in the Okta orgThe Okta container that represents a real-world organization.. The logo must be a .png, .jpg, or .gif file and have dimensions of less than 1400 by 400 pixels. It also must be smaller than 100 kilobytes in size.
   • App visibility — Choose whether to hide your integration from your end-users' homepage. Choose whether to hide your integration from the Okta Mobile Apps Store on your end-users devices.
   • App type — If your company created the integration and it is not intended for public use, select This is an internal application that we created.
2. Configure how your users sign in:
   • Who sets the credentials? — Choose who sets the initial password and username credentials: your end usersEnd users are people in your org without administrative control. They can authenticate into apps from the icons on their My Applications home page, but they are provisioned, deprovisioned, assigned, and managed by admins. or your org administrator.
   • Application username — Choose the format for the default username value when assigning the integration to end users.
   • Update application username on — At what point is the username updated in the integration.
3. Click Finish.

Next steps

• If your SWA integration is successful, when end users click the tile in their dashboard, the username and password fields are populated and the user signs on to the app automatically.
• If your integration does not behave as expected, contact Okta support at support@okta.com for assistance.
• Assign and unassign apps to users
• Assign apps to groups
• Submit an app integration to the OIN