What is the challenge? |
The current approach requires setting up a "service account" in our SSO then authorizing a user to checkout the password to setup connections |
---|---|
What is the impact? |
Setup friction less trust from security teams |
Describe your idea |
we should be able to authorize "aha" as a service itself and configure without a SSO workflow |