[solved] Lost access to Cockpit with upgrade to 7.14.0 while using SSO

[paulbors]

Hey there Camunda users,

For those of you that make use of SSO, are you experiencing lost access to the Cockpit post upgrade to 7.14? All other UIs work fine, Admin, Tasklist. It appears to be just the Cockpit that is redirecting the user to the login page.

This older post explains how we use filters to implement our SSO solution:

Single Sign On implementation in Camunda

Is a two fold problem. REST API: @Component public class StatelessUserAuthenticationFilter implements Filter { private ProcessEngine processEngine; private UserEntitlements userEntitlements; @Autowired public void setProcessEngine(ProcessEngine processEngine) { this.processEngine = processEngine; } @Autowired public void setUserEntitlements(UserEntitlementsImpl userEntitlements) { this.userEntitlements = userEntitlements; } @Override public void init(FilterConfig filter…

I’ve tacked it down to the 404 generated by the GET /user/{id}/profile which it appears to be querying inside Camunda’s DB for the user:

camunda/camunda-bpm-platform/blob/6fd62f5c7492b98f0187f0392dc1ea2a94342cda/engine-rest/engine-rest/src/main/java/org/camunda/bpm/engine/rest/sub/identity/impl/UserResourceImpl.java#L55

Has the Cockpit changed from 7.13 to 7.14 that would cause this? It was working fine before in 7.13 even with the 404 response from /user/{id}/profile.

More so, what’s the recommended way to implement SSO then if some of those endpoints are still attempting to read user profiles form Camunda’s schema?

[paulbors]

Okay I see, it’s not correct to use Filters here because the default identify service is still going against the DB.

Thus we must implement our own custom identify service and still use a filter to register it for Camunda UIs to pick it up. By default the engine picks it up.

[Niall]

Thanks a lot for filling us in on the your solution!