Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Search results

Page title matches

Page text matches

  • ...nerated SQL'' setting, and they will be able to specify whether the curent Authorization ID should be used as the current schema or enter the current schema name by :- ''Use authorization ID as current schema''. This says that the current authorization ID should be used as the current schema.
    6 KB (1,059 words) - 11:34, 27 September 2007
  • ===Authentication and Authorization=== *Ties into authorization discussion.
    7 KB (1,031 words) - 14:09, 12 October 2007
  • == Authorization, Access Control ==
    6 KB (808 words) - 16:36, 25 April 2011
  • ...ile service and security in these areas. Working on an authentication and authorization theme. Doing the workflow. Would like a minimal Node Orion file service.
    2 KB (295 words) - 16:13, 16 July 2012
  • ...ation for the User to make an informed decision regarding registration and authorization of the XRDS Provider, the ISAP Provider, and the IA Provider.
    7 KB (1,070 words) - 16:30, 12 December 2007
  • ...n-centric authorization grouping of users (while group is a resource-based authorization grouping of accounts). # Authorization
    5 KB (735 words) - 14:56, 15 January 2008
  • ...authorization mechanism can easiliy be extended later, to allow for other Authorization schemes. ** An implementor of a new authorization scheme must add an extension point to their headless space provider plugin
    19 KB (3,221 words) - 16:53, 21 January 2008
  • IdAS provides APIs to access identity attributes, but currently ignores authorization in terms of defining an access control model, defining management APIs, and ...de access to backing data stores which themselves incorporate some kind of authorization model, but these vary widely in capabilities and model.
    10 KB (1,541 words) - 15:11, 18 July 2009
  • === How COSMOS enables authentication / authorization / encryption for its Web UI === === How COSMOS enables authentication / authorization / encryption for embedded-approach adopters ===
    1 KB (167 words) - 17:47, 28 May 2008
  • ...er in the backing store as a sufficiently privileged user and then use the authorization characteristics of that user for all subsequent requests.
    9 KB (1,438 words) - 12:56, 24 January 2010
  • Security has many aspects. This document addresses authentication, authorization and session handling. Not included are SSL certificates or encryption in an ...already provides a good set of classes for dealing with authentication and authorization
    4 KB (683 words) - 03:49, 8 July 2011
  • ** Authorization query method? e.g. "boolean isAllowed(URI attributeType, <operation>)"
    3 KB (426 words) - 18:38, 28 October 2009
  • ...have attributes such as priority, funding/ccn, user community, complexity, authorization, and etc that can be set independently of workflows that are part of the go
    554 bytes (88 words) - 12:58, 8 May 2009
  • authorization properties.
    6 KB (1,015 words) - 07:58, 17 April 2008
  • ...or executing code. Not talking here about security holes, authentication, authorization etc
    26 KB (4,032 words) - 17:15, 19 May 2008
  • ...on in multiple phases. This overall solution will address Authentication, Authorization, and Encryption at the MDR, Broker, and UI/Client level. There is also a s
    3 KB (391 words) - 16:00, 16 May 2008
  • We need an implementation that supports authentication ONLY (no authorization, encryption is nice to have). One of our initial adopter products has a we
    15 KB (2,077 words) - 10:05, 23 May 2008
  • *org.remotercp.domain.authorization *org.remotercp.domain.authorization
    6 KB (910 words) - 07:20, 11 July 2011
  • #* There were use cases described that moved beyond simply using cards for authorization. These cases involved the user granting permission for service A to consume
    7 KB (1,068 words) - 21:42, 7 July 2008
  • ** some refactoring for authorization were done
    71 KB (10,112 words) - 06:43, 12 June 2012

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)

Back to the top