Warning!
You’re now reading a legacy document. The features described below are only usable within the classic generation environment.
Do you need an application template with the same or similar functionality? Follow this link to leave a request!
After reading this article you’ll know how to:
Create an application with an Okta sign-on login method
Set up SSO configurations
Use two main login methods
Description
Single sign-on (SSO) is an authentication method that allows users to securely log in to different services using a single ID. Using SSO means a user doesn't have to sign in to every application. With SSO, they can access all needed applications without being required to authenticate using different credentials.
Okta is an identity management service built for the cloud, but it gives access to many on-premises applications as well. Using Okta, an enterprise can easily manage its employees’ access to any application or device. Okta service provides single sign-on access to cloud-based applications through its own integration network (OIN). The integrations can use OpenID Connect, SAML, SWA, or certified APIs for SSO.
This article provides you with all the information you need to start using the Okta single sign-on template so all of your users can log in with their existing company account. It also has a regular login and registration workflow built in. The documentation will help you configure the last steps to get it up and running.
Use of template
Using the Okta single sign-on makes it easy to manage your application lifecycle. New user accounts for cloud apps are created with the correct access level. As people change job roles or leave, Okta automatically changes or removes their access to applications and services based on these identity changes. Okta SSO makes your systems more secure and saves time for your IT team, because of automation, integration, and password resets.
If you are constantly working with partners and vendors, Okta SSO might be a great asset. Don’t waste time onboarding your partners to give them limited access you need, organizations can use this single sign-on to connect with their own identity system. They would be able to manage identities for their users in the same way.
Pages overview
Home. The homepage of your application.
My Account. The page to edit your personal information and update your password.
SSO Redirect Page. This page redirects you to the Okta SSO login page.
User Login - Create New Account. The page to create a new user’s profile.
User Login - Login. The start page of your application via which registered users can log in using their credentials.
User Login - Password Reset Request. Using this page you can request to reset your password; a special link will be sent to your email address.
User Login - Reset Password. The page with reset password form; here users can create a new password.
Getting started with Okta SSO template
Creating application
Open My Betty Blocks and see your dashboard with suggested application templates in the ‘Start building’ section. Choose
Note: If you want to see the template’s live preview, click on its thumbnail, and in an open window find the |
The next steps will include coming up with a name for your application and setting a value for the application ID configuration. Find out why you need this setting and how to configure it properly in the Introduction to application templates article. |
Configuring SSO
In the next step, you will need to configure your SSO settings before everything will be up and running. To do this first you have to click on |
In a pop-up window, the four values need to be filled in:
App id: The unique identifier you gave your app. This is the same as you fill in before at the configurations tab.
Okta Domain: This is your organization's name of Okta. How to find your Okta domain check out this page.
Client: A client ID is an identifier associated with an application that assists with client/server authentication.
Secret Key: The client secret is a key that is used to encrypt exchanges between the server and the client.
Note: You shouldn’t publicly share your private key with anyone as they could use it to get access to your application without permission. |
The first one is your already known application ID, the rest can be found and retrieved from Okta’s admin panel after setting application integration there. How to do that is well explained in the Betty Blocks video course or Okta’s official documentation.
Once you’ve set up everything on the Okta platform, it’s time to copy the needed values to our SSO configuration.
Open your Okta’s application general settings and find the generated client credentials and copy them to your SSO configuration values fields. It is also recommended to save them somewhere separately in case you need them in the future. |
Click the |
User login methods
Everything is set up and now we see that this template offers two ways to login:
Standard login method: using an email and password
Single sign-on login method: the one you have just configured after following the documentation
Standard login
This way to log in is done using the email and password fields on the login page. New users can be created by clicking on the ‘Register new account’ and filling it out.
This user will be able to log in with their email and password.
Note: If you use the email address for this method, it cannot be re-used anymore for an SSO login.
Single sign-on login
The SSO login is processed by pressing the ‘Okta login’ button on the login page. The user will be redirected to the Okta sign-in page. Here the user can log in with their corresponding account.
After the first successful login, a new user will be created in the application.