| Info |
|---|
*Driver app support for new identity provider is still in progress. |
This questionnaire assists in initializing the Ocean’s identity provider. Configuration documentation - Configuration Guide
Instance details
Company name:
Brand name:
Migrate users
Operators: YES / NO
Migrate existing ones: YES / NO
Send all operators email to set new password: YES / NO
*Drivers: YES / NO
Migrate existing ones: YES / NO
Send all drivers email to set new password: YES / NO
Fleet managers: YES / NO
Migrate existing ones: YES / NO
Send all fleet managers email to set new password: YES / NO
External Identity providers
For identity brokers write only name, integration details will be discussed separately.
...
Social logins (e.g., Facebook, Google, ….)
Operator app:
*Driver app:
Fleet manager app:
...
Follow configuration documentation to fill out the form - Configuration options for your OCEAN's IdP
Start migration to Ocean’s IdP by sending us configuration details via JIRA
| Tip |
|---|
To fill out the form, open a new support ticket in JIRA and select “Setup for Ocean’s Identity Provider” option. You will get a table template you see below which you can edit. |
Configuration Template
INSTANCE DETAILS | |
Company name | Type in your company name |
Brand name | Type in your brand |
EXTERNAL IDENTITY PROVIDERS | |
Social Logins (ex: Facebook, Google, …) | |
Operator app Specify if you would like to use SSOs on your login forms and which for Operator app | YES/NO If YES, type which ones: Facebook, Google, … |
*Driver app Specify if you would like to use SSOs on your login forms and which for Driver app | YES/NO If YES, type which ones: Facebook, Google, … |
Fleet manager app Specify if you would like to use SSOs on your login forms and which for Fleet manager app | YES/NO If YES, type which ones: Facebook, Google, … |
Identity Brokers (ex: Azure, Okta, Keycloak, Auth0, … | |
...
) | |
Operator app Specify if you would like to use Federation login on your login forms and which for Operator app | YES/NO If YES, type which ones: Azure, Auth0 … |
*Driver app Specify if you would like to use Federation login on your login forms and which for Driver app | YES/NO If YES, type which ones: Azure, Auth0 … |
Fleet manager app Specify if you would like to use Federation login on your login forms and which for Fleet manager app | YES/NO If YES, type which ones: |
...
Email settings
Template
...
Account:
...
Azure, Auth0 … |
* Driver app support for new identity provider is still in progress.
EMAIL SETTINGS | |
Template | |
“From” email address Specify email address (ex: name@domain.com) you would like to send emails from | Type in |
“From” display name (optional) Specify display name (ex: | |
...
Company Name) you would like users to see when they receive emails | Type in |
“Reply to” email address (optional) Specify email address (ex: |
...
name@domain.com) you would like users to reply to your emails | Type in |
“Reply to” display name (optional) Specify display name (ex: Company Name) you would like users to see when they reply to your emails | Type in |
Email settings - Connection | |
Host | |
...
Type in | |
Port |
...
Type in | |
Encryption: | Enable SSL: YES / NO Enable StartTLS: YES / NO |
Authentication |
...
...
User name: Type in Password: |
...
Themes
Login themes
Identity provider contains default login theme - mobility brand and identity brokers are instance specific:
...
Type in | |
THEMES | |
Additional customization | YES / NO |
Email themes | Please, provide email customizations (texts, design). |
...
LOCALIZATION | |
Supported languages | |
...
Type in | |
BRUTE FORCE DETECTION | |
When detected brute force: | Lockout permanently |
...
or |
...
or |
...
or None |
Max login failures (default: 30) |
...
Number of allowed login failures | |
→ Additional settings can be overridden | |
...
...
...
...
PASSWORD POLICY | |
Password | |
...
requirements Specify which password requirements you would like to use | Type in |
→ For options see documentation https://landisgyr-evsolutions.atlassian.net/wiki/spaces/ | |
...
...
...
Password requirements:
OTP policy
...
OTP POLICY | |
Enabled | YES / NO |
Mandatory | |
...
YES / NO | |
→ Additional settings | |
...
...
...
...
...
CUSTOM DOMAIN ADDRESS | |
Identity provider login form is served from: auth-[eu|oce].etrel.com. If you want to use custom, brand related domain e.g., emobilitybrand.auth.com, add DNS CNAME record to auth-eu.etrel.com or http://auth-oce.etrel.com (based on your location) and we will whitelist your custom domain on our proxy. | |
Usage of custom domain | |
...
YES / NO | |
Custom domain Specify custom domain name (ex: |
...
domain.com) | Text |
CUSTOM LIFETIMES | |
Access token lifespan | |
...
| Insert time if want to customize |
Session |
...
Insert time if want to customize | |
Session max |
...
|
...
Insert time if want to customize | |
Initiated action lifespan |
...
|
...
reset password link |
...
validity) | Insert time if want to customize |
User Migration add-on template
| Info |
|---|
Fill out this template only if you had existing users in old Ocean’s platform database and you want to migrate users to Ocean’s IdP. For more detail see Migration from old OCEAN platform database to OCEAN's Identity Provider |
USER MIGRATION TEMPLATE | |
Operators | |
Migrate existing operators | YES/NO |
Send all operators to set new password If YES, all operators will receive an email to reset their password once migrated to Ocean’s IdP | YES/NO |
Drivers | |
Migrate existing drivers | YES/NO |
Send all drivers to set new password If YES, all drivers will receive an email to reset their password once migrated to Ocean’s IdP | YES/NO |
Fleet managers | |
Migrate existing fleet managers | YES/NO |
Send all fleet managers to set new password If YES, all fleet managers will receive an email to reset their password once migrated to Ocean’s IdP | YES/NO |