Okta Configuration
In Okta, create a new App Integration for the b4 admin site.
...
Copy generated Client ID and Client Secret and save the hotel’s domain value. For example, 'testhotel.okta.com':
...
When setting up Okta access, engage the b4 Support team via email - you have completed those steps, email support@b4checkin.com. This will to open a support ticket at b4 and our support team can will then complete the set up after these 2 steps are completeat our end.
To note
Note: Okta login to the b4 Admin tool only works from the hotel's Okta portal. The current "Sign in with Okta" button on our b4 Admin login page uses the default Okta organization, which may be different from your own.
...
b4 Okta Connection
Please provide the Okta configuration details below to b4 for onboarding.
Required b4 settings:
Assigned Properties - all b4 sites which may authenticate against Okta
Organization Domain - the Okta domain used for authentication
Client ID - created during application setup within Okta
Client Secret - created during application setup within Okta
Optional b4 settings:
Authorization Server ID - default is “default”
Scope - default is “openid;profile;email”
Optional b4 settings (multiple Okta domains):
Available Okta Domains (per-user) - used when restricting specific users to specific Okta domains
Default Okta Domain (per-property) - used when logging in through the generic admin portal
Default Okta Domain (per-user) - used when logging in through the generic admin portal
| Info |
|---|
NOTE: Updates to an Okta configuration may require up to 24 hours to fully propagate through b4 systems. This process can be expedited by contacting b4 support. |