Ripple Training & Certification Integration

Introduction

The Ripple Training & Certification module is now available from the Adonis Personnel Crew portal. When given access rights, crew members can access the RLD from a tile, which launches in a new tab in the user's browser. If the user does not yet have an account in the RLD, the user will be created. This behaviour can be switched off when the RLD synchronises with the office.

1 Introduction
2 Functionality
3 Housekeeping
- 3.1 Settings in APP
- 3.2 Access Rights
- 3.3 Configuration Ripple Training & Certification

Functionality

User logs in to the crew portal using their PIN and password.

On the dashboard, the user can see the “Ripple Training & Certification” tile, which provides access to the learning system.

After clicking the tile “Ripple Training & Certification,” a new tab will open, displaying the learning system as shown in the image below.

Housekeeping

Settings in APP

Configuration → General Settings → Ripple Training & certification

“Test” button only to test the URL, not the connection, for now.

Settings	Value

Settings	Value
Marine Learning System URL	<user LMS site>/services/api/oauth2/token example: https:\\ripplemariner.astaco.com/services/apioauth2/token
GrantType	password
Username	<user name>
Password	<password>
Scope	e.g. /Root/astaco
Interface	Ignore for now
Standalone Site	If checked, the system checks if the user exists; if not, it creates the user. The default operation mode is switched off.

Access Rights

Access rights are managed in the APP → Roles section, where the administrator can grant access to specific user groups.

Configuration Ripple Training & Certification

Org profile, CreateUpdateUser csv headers, super user creation, other?

Mandatory CSV columns

All column names are configurable within the LMS - no hardcoded constants required.

OrgLoginId
LastName
PasswordChangesAllowed (= false)

Optional CSV columns
Any additional column is optional (e.g., login email address, contact email address, organizational profile fields).

Current Limitations of the ‘Old’ User Importer

Creating new users via the current (old) user importer always sets the PasswordChangesAllowed=true which prevents the user to use the web login redirect. Therefore, all new users must be created via the API endpoint /Services/api/ExternalUser/CreateUser (Swagger reference).

Existing users can be updated in bulk via the current user importer (aka old user importer) because it doesn’t allow to set the PasswordChangesAllowed=false for users. No new users should be created via the bulk user importer.

Steps for Integration V2 (bulk import new users)

Use the the API endpoint /Services/api/ExternalUser/ImportCsvUsers (Swagger reference) instead of /Services/api/ExternalUser/CreateAndUpdateUsers to import users (update existing or create new users).
If new users are created, they need a column Password to be able to set a specific password for the user.
Set up the new user importer (to be able to set PasswordChangesAllowed=false)
- The new user importer must be configured to always set PasswordChangesAllowed=false for new users.