Minutes: GWS Telecon 2022-02-16Attendees:
| ||||||||
Changed: | ||||||||
< < | | |||||||
> > |
| |||||||
Preliminary List of Items:
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Discussion | ||||||||
Added: | ||||||||
> > | SSO Next generation: Descoping the security method and capability method that is part o f VO dataservice and VOSI We are adding something that can be added to the standard. What happens to the actual services running that have VOSI capability (SecurityMethod)? Only a few project are using The Registry does not need to advertise services with SSO capabilities. Just the client server interactions may require to use SSO http header. If Sara Bertocco can work as editor maybe Brian, Pat and Mark can make pull request for what they want to propose. And Sara can review the pull request and make sure the text is clear (work as editor role). Pull requests will address one or more issues. March is trying to involve ESA for GAIA Activity on scoping the tocken, we need use cases for that, it is a bit ambiguos to work with tockens, limiting the scope of the tocken is something important but it is matter for Credential Delegation. Default scope: proposal to limit the scope of a tocken into a domain. Expiration time and what happens after the exiration of the tocken (error message). Credential Delegation should be updated too Action: a new WD of SSO in early march. Execution planner: Brian read the Note, it is inetresting and he is willing to work on that. Unfortunately Dave is not present. In ESCAPE project there is some work done in execution planner. |
Minutes: GWS Telecon 2022-02-16Attendees:
Preliminary List of Items:
Discussion |