Conversation
There was a problem hiding this comment.
Pull request overview
Adds a developer guide describing how to locally test User Activity Service (UAS) endpoints in Simorgh, covering auth/session handling and CORS constraints commonly encountered in local environments.
Changes:
- Introduces new MDX documentation for local UAS endpoint testing
- Describes local-only workarounds for token refresh, cookie/token handling, and CORS
- Adds a troubleshooting section and resource links for further reading
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
elvinasv
left a comment
elvinasv
left a comment
There was a problem hiding this comment.
We could probably also mention that ckns_id is needed, otherwise we'll hide the UAS button (at least for now)
| }); | ||
| ``` | ||
|
|
||
| ### Local Development Workaround: Authorization Bearer Header |
There was a problem hiding this comment.
Is this part needed? I think it will work locally if we follow Step 3: Obtain and Store Authentication Token steps, therefore Authorization header shouldn't be needed?
There was a problem hiding this comment.
Yes, these are required.
Simply copying and pasting the ckns_atkn cookie won’t be enough to trigger UAS locally.
We also need to include the Authorization header steps, as this won’t work locally.
There was a problem hiding this comment.
Are you referring to the token refresh or UAS GET/CREATE requests? I was able to run it locally without adding Authorization header 🤔 #13890 (review)
Resolves JIRA:
Summary
A Guide that provides instructions for developers to test User Activity Service (UAS) endpoints locally
Testing UAS endpoints locally requires several setup steps to handle authentication, CORS issues, and session management.
This document outlines all necessary configurations.
Included some Troubleshooting steps as well