On This Page
Now that you've built an app, get it ready to launch!
By now, you might have built your first app with Okta, congrats! There are just a few final steps for you to take to customize your app and get it ready to launch. The guides below help you take your app to the finish line.
Here's your pre-launch checklist:
Ensure your application fits your brand:
- Use a custom domain: Customize your Okta organization by replacing your Okta domain name (for example, dev-12345.okta.com) with your own domain name (for example, id.example.com) so that all URLs look like your application.
- Customize and add branding to your sign-in page: Tailor the sign-in page to fit your brand or your application's look and feel so that your user experience is consistent and seamless.
- Customize and add branding to your error pages: If an error occurs during sign in, Okta may need to display an error page to the user. Customize the error page to match the rest of your app.
- Email domain setup: Update the "From" address and domain of the emails sent to your users.
- Customize email templates: Change the look and feel of the emails sent to users by Okta.
- Manage access to protected resources: If your app has to validate the signed tokens that are issued to end-users. Learn about this process and best practices for validating your user's tokens.
- Update Redirect URI for your domain: If you created an Okta application that uses
localhostor a test domain, you need to update your Okta application (or create a new one) using publicly accessible URLs.
- Configure Cross-Origin Resource Sharing (CORS): If you are building a SPA or you are embedding the Okta Sign-In Widget into your own app, you must configure CORS for your domain.
Note: Configuring CORS isn't needed if you are using Okta's custom domain feature.
- Configure Multi-Factor Authentication (MFA): Set up which security factors are used when users sign in.
- Set up Self-Service Registration: Allow users to sign up for an account with an email address.
- Enable Social Authentication: Allow your users to sign in with their other services.
- Review how Okta's rate limits work: Requests made to the Okta API have rate limits to prevent abuse.
Okta provides a set of reports and logs to help you troubleshoot user problems. These reports are available in the Classic UI.
If the top of your Okta Admin Console says Developer Console, click the drop-down box and select Classic UI.
- View activity and security reports (opens new window): Help diagnose sign-in problems for your users.
- View events in the System Log (opens new window): To see a more general log of all events in your Okta organization.