Hi team,
Can anyone help if we have missed anything while setting up SSO for our Camunda app?
- Implemented SSOAuthenticationProvider which implements AuthenticationProvider class. Ensured to add authentication objects to session. Also made sure to add userId as part of AuthenticationResult.
- Added ContainerBasedAuthenticationFilter with init-param as the new authentication provider
<filter>
<filter-name>AuthenticationFilter</filter-name>
<filter-class>org.camunda.bpm.webapp.impl.security.auth.ContainerBasedAuthenticationFilter</filter-class>
<init-param>
<param-name>authentication-provider</param-name>
<param-value>SSOAuthenticationProvider</param-value>
</init-param>
</filter>
<filter-mapping>
<filter-name>AuthenticationFilter</filter-name>
<url-pattern>/*</url-pattern>
<dispatcher>REQUEST</dispatcher>
</filter-mapping>
With above changes though redirect happens to SSO and code successfully executes SSOAuthenticationProvider, it redirection back to Camunda Login page again which shouldn’t have happened given we have already authenticated. I couldn’t find any failure logs within the app.
I followed the steps mentioned here Securing Camunda 7 | Camunda 8 Docs
Do we need make any other modifications to make sure user is authenticated and bypass Camunda login?
Any leads would be of great help!
Thanks & Regards,
Srikar Rampally