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
Many publishing plugins (Azure, PVA, Github) will require authentication to a given service in order to carry out the actions.
It should be possible for the plugin to require a specific type of authentication, and for this authentication to be separate from the bulk "access restriction" authentication currently available through the auth plugin.
It should be possible, for example, to require auth to Github to publish to Github and have this handled as an in-app flow.
Describe the solution you'd like
Allow a publishing plugin to return a 401 or 403 header and redirect to specific login page
Introduce ability to expose auth endpoints but not require them for access (that is, do not apply them by default, just enable them to be used to unlock specific capabilities)
Figure out a secure way for Composer to store login credentials like this
The text was updated successfully, but these errors were encountered:
Many publishing plugins (Azure, PVA, Github) will require authentication to a given service in order to carry out the actions.
It should be possible for the plugin to require a specific type of authentication, and for this authentication to be separate from the bulk "access restriction" authentication currently available through the auth plugin.
It should be possible, for example, to require auth to Github to publish to Github and have this handled as an in-app flow.
Describe the solution you'd like
The text was updated successfully, but these errors were encountered: