This document outlines the process for migrating Operator users to the new Ocean identity provider.
| Tip |
|---|
If you want to migrate your users to Ocean’s IdP, please send us filled form via Jira ticketing system: Migration document |
Initial migrations
All Operator users are currently stored in Ocean’s platform database. To migrate these users to Ocean’s identity provider, we use a migration service. This service transfers the Operator users to Ocean’s identity provider, creates corresponding user accounts, and assigns them the land_operator role, which is necessary for accessing the Operator portal.
...
| Tip |
|---|
If you want to migrate your users to Ocean’s IdP, please send us filled form via Jira ticketing system: Configuration Template for OCEAN's IdP |
Syncing Operator Changes with Ocean’s identity provider
Operators within the Ocean platform can be deleted, updated, or added. All these changes are automatically synchronized with Ocean’s identity provider, ensuring that the user data remains consistent across both systems.ak.
...
Operator registration
All operators must first be added to the Ocean platform, where their user profiles are created. This identity information is then automatically transferred to the Ocean’s identity provider through integration services.
External Provider Login
In operator portal operators can have “Is external federation account” flag enabled. This flag is synced with Ocean Identity provider - user gets special role land_brokered_identity, which marks that user can login with external provider.
To find this setting go to Ocean → Security → Access management → Choose one operator → Find this setting:
...