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
We need to update our OpenAPI documentation to accurately represent how our token is formatted.
Under the 'Available Authorization' > 'serviceAuth', the follow text should be updated:
"The format of this token is {key_name}-{iss-uuid}-{secret-key-uuid}. should be updated to "The format of this token is "Bearer <value>".
Ticket is understood, and QA has been contacted (if the ticket has a QA label).
User Story(ies)
As a VANotify developer maintaining the Notification-API repo I want to update the OpenAPI documentation on token formatting So that the documentation reflects our tokens formatting accurately.
Additional Info and Resources
See notification-api/documents/openapi/openapi.yaml
User Story - Business Need
We need to update our OpenAPI documentation to accurately represent how our token is formatted.
Under the 'Available Authorization' > 'serviceAuth', the follow text should be updated:
"The format of this token is {key_name}-{iss-uuid}-{secret-key-uuid}.
should be updated to"The format of this token is "Bearer <value>".
User Story(ies)
As a VANotify developer maintaining the Notification-API repo
I want to update the OpenAPI documentation on token formatting
So that the documentation reflects our tokens formatting accurately.
Additional Info and Resources
notification-api/documents/openapi/openapi.yaml
Acceptance Criteria
QA Considerations
Potential Dependencies
The text was updated successfully, but these errors were encountered: