 Link this issue to another issue
|
|
If you were logged in you would be able to see more operations.
|
|
|
We need an ability to do the following which should be called "authentication-ticketing":
- let, within the ActiveMath world, the authentication framework generate a secure ticket number given an authenticated user
- this can be exchanged through many different channels, including through (trusted) third-parties
- an http request should be able to be added with a ticketId=<ticketNumberDeliver> and would thus, automagically send a redirect with all needed cookies set thus transforming our http-request into an authenticated request
- the ticket should then be consumed.
This is useful for an applet or jnlp-program on the client to make authenticated http requests (they don't have browser cookies) and in some other situations.
|
|
Description
|
We need an ability to do the following which should be called "authentication-ticketing":
- let, within the ActiveMath world, the authentication framework generate a secure ticket number given an authenticated user
- this can be exchanged through many different channels, including through (trusted) third-parties
- an http request should be able to be added with a ticketId=<ticketNumberDeliver> and would thus, automagically send a redirect with all needed cookies set thus transforming our http-request into an authenticated request
- the ticket should then be consumed.
This is useful for an applet or jnlp-program on the client to make authenticated http requests (they don't have browser cookies) and in some other situations. |
Show » |
|
New Feature
Closed
Major
Authentication Tickets
