database - What's a "single sign on" table used for and why is this column list necessary? -
I was looking at a schema and was trying to figure out how to use this table Make the "code" "single_sign_OnS" "token" is not VARCHAR (64), "IP" VARARAR (32) No, zero, "expired", not DATETIME, "one_time" VARCHAR (64), "created" DATETIME, "updated_at" DATETIME, "user_id" integer, primary key ("token");
What is "single sign on" and why did the author of this table include these columns for this purpose?
This is a holder for the user's sign-on session. I believe that when a user signs in to verify that his session is still active, and allows access to various servers / sites without entering a second time.
I'm assuming earlier on login, the user's session will be known to be new, so that the user will be inquired for credentials. Then a line has been entered in this table, containing the user id, the IP address, the date of creation, and a token. This token will be connected to the user's session and will be used in subsequent logins.
The other process will then receive the token as part of the communication and to ensure that the session is still valid, check this table. When the session is checked, the update field will change, so that the user is known to be active.
However, more logic will periodically check the table and will not end any session rows that have not been updated Recently enough which is "sufficient" for this system then token Along with the expiration date for access requests, queries for credentials and a new line with a new token.
Comments
Post a Comment