Story (Required){}

Use backstage login information. LightSpeed frontend plugin calls LightSpeed backend plugin through FetchAPI, and backstage will include a token in that call. 

According to a backstage issue comment, user entity need to be defined if we want to get user details, the user entity name can be served as user_id

This story includes verification on the token, and also verification on login user and passed in userid.

Background (Required)

<Describes the context or background related to this story>

_Chat is authenticated for access by individual user only, e.g. by RBAC authentication or RHDH login information.
_

Out of scope

multi-user authentication

Approach (Required)

<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

Dependencies

<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

Acceptance Criteria (Required)

<Describe edge cases to consider when implementing the story and defining tests>

<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

documentation updates (design docs, release notes etc)
demo needed
SOP required
education module update (Filled by DEVHAS team only)
R&D label required (Filled by DEVHAS team only)

Done Checklist

Code is completed, reviewed, documented and checked in
Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
Continuous Delivery pipeline(s) is able to proceed with new code included
Customer facing documentation, API docs, design docs etc. are produced/updated, reviewed and published
Acceptance criteria are met
If the Grafana dashboard is updated, ensure the corresponding SOP is updated as well