Uwe Risse

Ok. Now we have another error message. I assume that you did not use the button "Continue with.." in your first post. "access token is not valid" means The configured client id from the JOC identity service is not equals with the field "aud" where the client id is returned from the Open Id Service Provider. or The configured client authentication url from the JOC identity service is not equals with the field "iss" where the url is returned from the Open Id Service Provider. or The account from the...

Ok. Now we have another error message. I assume that you did not use the button "Continue with.." in your first post. "access token is not valid" means The configured client id from the JOC identity service is not equals with the field "aud" where the client id is returned from the Open Id Service Provider. or The configured client authentication url from the JOC identity service is not equals with the field "iss" where the url is returned from the Open Id Service Provider. or The account from the...

Ok. Now we have another error message. I assume that you did not use the button "Continue with.." in your first post. "access token is not valid" means The configured client id from the JOC identity service is not equals with the field "aud" where the client id is returned from the Open Id Service Provider. or The configured client authentication url from the JOC identity service is not equals with the field "iss" where the url is returned from the Open Id Service Provider. or The account from the...

Ok. Now we have another error message. I assume that you did not use the button "Continue with.." in your first post. "access token is not valid" means The configured client id from the JOC identity service is not equals with the field "aud" where the client id is returned from the Open Id Service Provider. The configured client authentication url from the JOC identity service is not equals with the field "iss" where the url is returned from the Open Id Service Provider. The account from the login...

Please describe how and where you have configured the truststore path. Do you have created the client in Keycloak with client-protocol=openid-connect accessType=confidental Do you see the button "Continue with Keycloak"? If yes, have you clicked the button to login? When you try to login with keycload-oidc, do you see the keycload credentials form? Please enable debug logging (https://kb.sos-berlin.com/x/PMUwAw) and share the authentication-debug.log file. To find the log4j2 configuration file refer...

What security level have you in your JOC Cockpit environment?

Can you please try to identify the order when you click the "All Orders" filter in the Order Overview. Maybe this helps to see, why the order is so special.

This is reported in JOC-1734 Please check whether this workaround works for you Change the type of the identity service to LDAP Open Manage Settings view Submit the view without any changes Change the type of the identity service back to LDAP-JOC