David Geiger

See here for detailed instructions on adding a custom quirk: https://community.home-assistant.io/t/how-to-configure-the-philips-hue-wall-module-to-use-push-button-momentary-type-wall-switches-zha/451125/27

Sounds good to me. I believe both of the above examples (Amplify and gcloud CLI) open a browser window for an interactive OAuth auth code flow. I assume a similar...

Same here, this would be an important feature to reduce the number of password-based "service accounts". They may still be required for technical clients that cannot obtain a SAML token,...

Haven't thought this through, but perhaps it is feasible to create a simple wrapper around the apim-cli in order to turn it into an [Axway CLI extension](https://docs.axway.com/bundle/axwaycli-open-docs/page/docs/extensions/index.html)? A command such...

Any new thoughts on how to approach this? I believe an interactive authentication is crucial to ensure CLI usability with an SSO-enabled distributed setup. Having to request dedicated technical users...

Would it help to engage with the Axway CLI team to see if the same logic can be used? The need to create a technical username/password account for each user...

Hi @rathnapandi. I might have misunderstood but this doesn't seem feasible to me. A user's identity needs to be authenticated by the central identity provider. Otherwise, users can easily impersonate...

Hi @rathnapandi. I see several challenges with the described hybrid approach. It will not be possible to use private keys of our IdP. More generally, if the CLI issues or...

Re impersonation: If the CLI generates its own SAML assertions that are trusted by API Manager (signed or not), what prevents a user from changing the username in those assertions...

Agreed, an SP-initiated login with authentication requests generated by the CLI will not work if the IdP expects signed requests. Signing requests does not seem to add any value in...