Group items matching
in title, tags, annotations or urlFalcor: One Model Everywhere - 0 views
OpenAM Administration Guide - 0 views
-
An authentication service confirms the identity of a user or a client application.
-
OpenAM is most frequently used to protect web-accessible resources. Users browse to a protected web application page. An agent installed on the server with the web application redirects the user to OpenAM for access management. OpenAM determines who the user is, and whether the user has the right to access the protected page. OpenAM then redirects the user back to the protected page, with authorization credentials that can be verified by the agent. The agent allows OpenAM authorized users access the page.
authorization - SAML2 vs. OAuth - What are some reasonable relationships? - Information Security Stack Exchange - 0 views
-
Bridging the SAML and OAuth 2.0 frameworks is a well understood problem. The following stack of IETF specs provides a standard solution: If you look at the core OAuth 2.0 spec (RFC 6749) and its token endpoint definition - this is basically an OAuth server endpoint which returns an access token in exchange for a "grant" -- an open-ended concept of something deemed appropriate to grant the client app the issue of an access token. In the typical OAuth scenario this is an authorisation code signifying that the user has been previously authenticated and given their consent. But the grant could also be something else. There is a further IETF spec called draft-ietf-oauth-assertions-16 that builds on the core RFC 6749 standard which says that the grant can also be an assertion (a signed proof of something) and defines the necessary token request parameters for that. Finally, there is draft-ietf-oauth-saml2-bearer-20, which specifies how this assertion can be a SAML 2.0 Bearer Assertion. This standard mechanism for converting a SAML assertion into an OAuth 2.0 access token is essentially all that is needed to bridge the two frameworks. To ensure removal of users is properly reflected by the authorisation systems there are two approaches, which can be combined: Make the OAuth 2.0 access tokens short lived. This will force the client to repeat the authorisation process when the token expires, and if the user no longer exists authentication will fail and no grant (SAML assertion) will be issued. Provide an API for revoking issued OAuth 2.0 access tokens, see RFC 7009 for details.
-
Es un problemón conocido y con blancos sin estandarizar el juntar SAML 2.0 en cuanto a AuhN y Oauth2 para autorización. Éste post es el mas sintético que encontré con un agregado de valor muy alto: Deja entrever que aunque no sea estándar, el mecanismo es posible, y se basa en convertir una aserción SAML2 en un token de acceso OAuth2. uno puede transliterar ésta propocisión así: "convertir una aserción CLAVE FISCAL en un token de acceso OAuth2". La pregunta es: ¿Que será una aserción CLAVE FISCAL?
SSH Can Do That? Productivity Tips for Working with Remote Servers | Smylers [blogs.perl.org] - 1 views
-
these OpenSSH tips sound useful to you, it may be worth giving Copssh a try (or indeed switching to a dif
Gitblit - 1 views
-
Redmine authentication
-
"Gitblit is an open-source, pure Java stack for managing, viewing, and serving Git repositories."
-
Es una alternativa a analizar, pero como te comenté hoy, creo que sacando la -a priori- facilidad de agregado de módulos de autenticación (e integración con redmine), el resto de los features no son superiores a Git Lab 7. Hoy por hoy tenemos un ambiente Git Lab 7 que ni bien nos asignen fierros en sala cofre reemplaza al actual (versión 3.0). Luego de eso viene integración de redmine con sua. Salvo que veas razones de peso no me parece destinarle recursos hasta luego de integrar Redmine con SUA. No se que opinás.
Home - Haxe - The Cross-platform Toolkit - 1 views
« First
‹ Previous
61 - 73 of 73
Showing 20▼ items per page