You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Kong ACL only is currently used by a client that uses Siteminder to login. Other branch services also use it. This is valuable to include in the automation tests.
The text was updated successfully, but these errors were encountered:
As per discussion with Aidan, Kong ACL flow is applicable to SSO where user sign in with SIteMinder and based on user group on SSO Identity Management, Kong allow the user to allow or deny the service access.
In APS we uses API and Client Credentials as Authentication and uses Keycloak as Identity management, Kong ACL only would not be applicable. Even Siteminder would be rid off eventually moving to Keycloak
Kong ACL only is currently used by a client that uses Siteminder to login. Other branch services also use it. This is valuable to include in the automation tests.
The text was updated successfully, but these errors were encountered: