Currently, Plexus Connect supports three types of authentication:
Instant JChem based authentication:
This is the default method, where there is no need for any extra configuration. Each user will be authenticated against the configured Instant JChem schema(s). You can read more about configuring an Instant JChem schema here.
Anonymous authentication: In this case, users do not need to authenticate themselves when they log in to Plexus Connect; every user will be assigned to the same pre-specified user name.
To use this authentication type, set the following configuration property:
The default user name is "Guest" while the default user role is "ROLE_USER".If you would like to change the user name or the role, you have to use the following properties:
For example you can set the common user name as "Plexus user" and give data editing privilege to every user the following way:
In version 21.2.0 of Plexus Connect, the Oauth2 authentication method has been introduced. This method requires extra configuration on both sides Plexus Connect and Oauth2 authentication server. You can read more about configuring here.
In version 21.4.0 of Plexus Connect, the Windows authentication method has been introduced. This method requires extra configuration on both sides Plexus Connect and Kerberos on authentication server. You can read more about configuring here.
API keys authentication
In version 21.15.0 of Plexus Connect, the API keys authentication for using the API has been added, mostly for Scripting and for Schema refresh from the IJC. It works as a secondary layer of authentication, which works with all authentication types described above. Please find details about API keys here.