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
Create an API to allow SeaJell user to login with eKV credentials.
API request to eKV will be verified with an API key provided by eKV (use Sanctum if possible, idk if it is). This API key is bound to a hostname which is SeaJell hostname. If no API key or the hostname doesn't match with its hostname, eKV API will return an error.
The API will return with a response which consist of basic user information that SeaJell needed to function like user name, user identification number etc. The response will be saved into SeaJell database to reduce the amount of requests when regenerating e-cert for user.
The flow
eKV admin enable eKV Login API feature.
eKV admin generate an API key for the SeaJell hostname (for API key validation).
SeaJell admin enable eKV Login API and enter eKV hostname (for API request) and API key from eKV.
User tick the "Login with eKV" box on SeaJell login page which allows them to login with eKV credentials. This box will only appear when SeaJell admin enable eKV Login API.
Response from the API will be stored inside a special eKV user table in SeaJell database. The data in this table will be used for eKV user e-cert.
For now idk how SeaJell e-cert addition (individual or bulk) function will work and also how other SeaJell features will work. I'll think about this later.
The text was updated successfully, but these errors were encountered:
This feature is for v0.3.0
Create an API to allow SeaJell user to login with eKV credentials.
API request to eKV will be verified with an API key provided by eKV (use Sanctum if possible, idk if it is). This API key is bound to a hostname which is SeaJell hostname. If no API key or the hostname doesn't match with its hostname, eKV API will return an error.
The API will return with a response which consist of basic user information that SeaJell needed to function like user name, user identification number etc. The response will be saved into SeaJell database to reduce the amount of requests when regenerating e-cert for user.
The flow
For now idk how SeaJell e-cert addition (individual or bulk) function will work and also how other SeaJell features will work. I'll think about this later.
The text was updated successfully, but these errors were encountered: