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
Describe the bug
Currently setting the annotation on a sequence doesn't add the /adobeio/shared-validators-v1/app-registry action to the sequence and hence doesn't protect the sequence. Individual web actions "components" of the sequence should also be protected with the require-whisk-annotation
Workaround
A workaround is to configure the protection manually:
EDIT: See comments below, you may want to remove the require-whisk-auth annotation and remove the web option instead.
@shazron the idea is to protect the actions in the sequence, otherwise the sequence is not secured. It's one way of doing it, the other way would be to delete the web annotation (just like we do when parsing require-adobe-auth for non-sequences)
Describe the bug
Currently setting the annotation on a sequence doesn't add the /adobeio/shared-validators-v1/app-registry action to the sequence and hence doesn't protect the sequence. Individual web actions "components" of the sequence should also be protected with the
require-whisk-annotation
Workaround
A workaround is to configure the protection manually:
EDIT: See comments below, you may want to remove the
require-whisk-auth
annotation and remove theweb
option instead.The text was updated successfully, but these errors were encountered: