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
When users deploy an extension using this action, they have to supply IMS Auth
Right now the action is only set up to support jwt credentials as it explicitly uses the private key and still uses the meta_scopes parameter when setting up the context in ims
We should add support for using OAuth credentials with this action since jwt has been deprecated
The text was updated successfully, but these errors were encountered:
When users deploy an extension using this action, they have to supply IMS Auth
Right now the action is only set up to support jwt credentials as it explicitly uses the private key and still uses the meta_scopes parameter when setting up the context in ims
We should add support for using OAuth credentials with this action since jwt has been deprecated
The text was updated successfully, but these errors were encountered: