For some OIDC Identity Providers, for example Azure, the permission assignment does not work.
The reason being that Azure does not provide the exact attribute of a user account that is expected by JOC Cockpit.
Desired Behavior
For use with Azure the JOC Cockpit falls back to using the "email" attribute of a user account.
In addition, with JOC-1525 users can specify with the Identity Service configuration in JOC Cockpit the name of the attribute that should be used from an OIDC Identity Service's response after successful authentication.
Fix
Major