task/WG-139: add uuid for guest users #155
Conversation
|
|
||
| Attributes: | ||
| username (str): A unique username for the anonymous user, prefixed by 'Guest_'. | ||
| If no `guest_unique_id` is provided, username defaults to 'Guest_Unknown'. |
There was a problem hiding this comment.
Under what conditions would this occur? Regardless of user vs guest state, every connected client session should have a UUID, right?
There was a problem hiding this comment.
Wouldn't the response to a null|none UUID value be to generate one? I don't see any conditions where a UUID should not be available. What am I missing?
There was a problem hiding this comment.
We are generating the uuid on the client side (i.e. hazmapper/taggit) and then adding to all requests (we put it in 'X-Guest-UUID' in the header). So if someone else was making requests outside of taggit/hazmapper then there would be no X-Guest-UUID in the header. So interacting with the geoapi outside of the 2 clients would make it Guest-Unknown.
Overview:
Add uuid for guest users
Related Jira tickets:
Summary of Changes:
Testing Steps:
Get features of project:2 for user:Guest_5669ae1c-a292-4bf2-b09b-fc63d6f86e10)