After the introduction of Single Sign-On (SSO) login, several changes were made to the API authentication. In addition, the SSO login also affects when logging in to a plugin, such as Rhino, Grasshopper, or Revit.
Logging in to integration plugin (e.g. Rhino, Revit)
In order to log in to any plugin, one must create a plugin password (currently called 'Get temporary password', also called API password or API key) in the One Click LCA user profile page (see screenshot below) and this password should be used when logging in for a 2-way connection. This password can be created as many times as needed or you can use the password you have generated once in order to log in to the plugin in the future. If you are logging into One Click LCA with a username and password rather than SSO, note that this temporary password will not replace your One Click LCA user account password.
Moreover, the API and UI authentication are now separated. The API login endpoint does not change however the password used will be different. The API user does not log in with their normal password but will have to create a temporary password instead.
The temporary password can be created on your user account page.
When the user clicks 'get temporary password', a secure password is created and copied to his/her clipboard. This password should be used when login in using API.
A new temporary password can be created as regularly as the user wants. The temporary password is activated immediately upon creation.
Note: The API authentication works with the old password for some time. However, since the API authentication is no longer linked to the user's UI password, changing the user's password does not change the API password.
If API is used for one-way integration, i.e, the user submits the resources via API and then uses the browser to import them, the user is redirected to the login screen before getting access to the application.
After a successful login, the user is redirected to the import page, as before.