...
This feature is accessible via the homepage under the "Feature Shortcuts" section, labeled “PRISMS.”
...
1) Meshed Platform PRISMS Integration Configuration
The API service uses standard (OAuth) authentication using Azure B2C as the secure token service to gain access to PRISMS services. This workflow verifies the credentials for a user to access PRISMS API by logging into PRISMS using their email address, password and Multi- Factor Authentication (MFA) in a web page.
...
Meshed Compliance Connector Integration Setup
PRISMS API Subscription Details
Client PRISMS Credentials Configuration
1.1) Meshed Compliance Connector Integration Setup
These details are configured by the Meshed team and cannot be modified or viewed by the end user.
1.2) PRISMS API Subscription Details
...
The API service requires the PRISMS Client ID and PRISMS OCP-APIM-Subscription-Key which is unique to each provider.
These API key details should be provided to the Meshed Support Team to help you set up the API service. Once configured, these details can be viewed by end users, but cannot be modified.
1.3) Client PRISMS Credentials Configuration
This section contains the user configuration details for each user who tries to authenticate and log in with PRISMS. The Meshed user log in will be saved along with the PRISMS Client ID used by each user to access PRISMS for data integrity.
2) Authenticating with PRISMS
Once the above authentication details are recorded in the Meshed system, a user can proceed to authenticate with PRISMS.
PRISMS User Authentication requires the users to provider their PRISMS login details that can authorise them as CoE Administrator or CoE Create users. Failure to supply correct PRISMS login details will halt the authorisation process implying that the integration cannot be used by the specific user.
2.1) First-Time User Authentication
When a user logs in to the Meshed system and proceeds to use the PRISMS API service, the PRISMS API Subscription Details section will be pre-populated with the API subscription details and will prompt the user to click on the “Set PRISMS Credentials” button as shown below.
...
After the PRISMS credentials are successfully set for the user, the next step is to Authorise with PRISMS using valid PRISMS login credentials.
...
The user can now continue to use the integration service in the Meshed system.
2.2) Existing User Authentication
For a user who has used the PRISMS API integration in the Meshed system before and is not a first-time user, the authentication process is a little different.
The user does not need to click on the Set PRISMS Credentials button as the PRISMS API credentials are already stored in the system for the user.
The system will also display the PRISMS User Email used by the specific user as per his last successful login to PRISMS.
Click on Authorise with PRISMS button to start the authorisation process. The system redirects the user to PRISMS authentication where the process is the same as authenticating a new user. After successful authentication, the token is returned and the success message is displayed.
...
2.3) Token Generation and Validity
The token generated for each successful user authentication is valid for a period of 24 hours. This implies that each user must re-authorise with PRISMS once the 24-hour period elapses.
...