Service-dependent authentication filter #6

New Issue

Open

opened 2020-11-14 08:46:34 +01:00 by nolash · 2 comments

nolash commented

2020-11-14 08:46:34 +01:00

(Migrated from gitlab.com)

The browser needs to know what authentication token to choose for a particular query.

After unlocking of the staff PGP private key for a new session, the browser should transparently authenticate and gather tokens for with all the different services it knows about.

All queries needs to pass through this authentication component, so that tokens can be automatically refreshed as they expire.

Tokens should be filed under the corresponding "HTTP realm" the services announces.

This implies that the browser also needs to now which URLs match to which "realms."

The browser needs to know what authentication token to choose for a particular query. After unlocking of the staff PGP private key for a new session, the browser should transparently authenticate and gather tokens for with all the different services it knows about. All queries needs to pass through this authentication component, so that tokens can be automatically refreshed as they expire. Tokens should be filed under the corresponding "HTTP realm" the services announces. This implies that the browser also needs to now which URLs match to which "realms."

nolash commented

2020-11-14 08:47:23 +01:00

(Migrated from gitlab.com)

changed the description

nolash commented

2020-11-14 08:47:40 +01:00

(Migrated from gitlab.com)

changed the description