IVOA Grid & Web Services: Security



Though our data may have zero commercial value (according to Jim Gray), we are still concerned about who can access them and ensuring that they and the services that we provide are not exploited for nefarious purposes. However, users don't care about protocols and standards - they care about better experience with enhanced privacy and security. We require simple to use, robust, and scalable solutions to the issues of authentication (who am I), authorization (what can I do) and delegation (how do I allow someone else to do something on my behalf) that work with all kinds of services and applications that the VO offers.

Access control

The ability to control who has access to resources and what operations are permitted is a common task across the IVOA.

Prototype work on using HTTP headers to convey authentication: SSO_next


Edit | Attach | Watch | Print version | History: r8 < r7 < r6 < r5 < r4 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r8 - 2022-01-04 - PatrickDowler
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback