Allow OIDC/SAML Federated login to developer console
Allow OpenID Connect or SAML federated login to Alexa Developer Console.
We have several teams in our organization who are starting to work on skills that they intend to release publicly. Most other services we use support federated login using OpenIdConnect/SAML, but the Alexa Developer Console notably does not.
I know console access currently isn't currently structured in a way that federated login would make particular sense, but being able to say from my side "users in this AD security group can login to the Alexa Console and manage our skills" so they have access granted and revoked as they join and leave the organization/team would be great. Having to invite and remove "unmanaged" accounts for folks will become cumbersome as more people start using this.
Austin R. Frazier commented
I second this as well. We would integrate via SAML with Okta to secure our developers logging in.