Okta integration - single sign-on identity management

Okta Configuration

In Okta, create a new App Integration for the b4 admin site.

Open

Required settings:

• OIDC - OpenID Connect - true

• Web Application - true

• Client Credentials - true

• Sign-in redirect URIs - https://gettaroom.b4checkin.com/Admin/Admin/Okta/Login or https://euro.b4checkin.com/chameleon/Admin/Admin/Okta/Login

• Sign-out redirect URIs - https://gettaroom.b4checkin.com/Admin/Admin/Okta/PostLogout or https://euro.b4checkin.com/chameleon/Admin/Admin/Okta/PostLogout

• Login initiated by - Either Okta or App
  
  

Open

2. Copy generated Client ID and Client Secret and save the hotel’s domain value. For example, 'testhotel.okta.com':
   
   

3. When you have completed those steps, email support@b4checkin.com to open a support ticket at b4 and our support team will then complete the set up at our end.
   
   
   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