/usr/lib/python2.6/site-packages/keystoneclient/contrib/auth/v3
Edit: /usr/lib/python2.6/site-packages/keystoneclient/contrib/auth/v3/saml2.pyc (36561B)
Ñò
( ( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyR9 P s t Saml2UnscopedTokenc B s e Z d Z e Z d Z h d d 6d d 6Z h d d 6Z h d d 6d
d 6d d
6Z d Z d Z
d Z d Z d „ Z
e d „ ƒ Z e i d „ ƒ Z e d „ ƒ Z e i d „ ƒ Z d „ Z d „ Z d „ Z d „ Z d „ Z d „ Z d „ Z d „ Z RS( sö Implement authentication plugin for SAML2 protocol.
ECP stands for `Enhanced Client or Proxy` and is a SAML2 extension
for federated authentication where a transportation layer consists of
HTTP protocol and XML SOAP messages.
`Read for more information
`_ on ECP.
Reference the `SAML2 ECP specification `_.
Currently only HTTPBasicAuth mechanism is available for the IdP
authenication.
:param auth_url: URL of the Identity Service
:type auth_url: string
:param identity_provider: name of the Identity Provider the client will
authenticate against. This parameter will be used
to build a dynamic URL used to obtain unscoped
OpenStack token.
:type identity_provider: string
:param identity_provider_url: An Identity Provider URL, where the SAML2
authn request will be sent.
:type identity_provider_url: string
:param username: User's login
:type username: string
:param password: User's password
:type password: string
i s# text/html, application/vnd.paos+xmlt AcceptsM ver="urn:liberty:paos:2003-08";"urn:oasis:names:tc:SAML:2.0:profiles:SSO:ecp"t PAOSs application/vnd.paos+xmls Content-Types, urn:oasis:names:tc:SAML:2.0:profiles:SSO:ecpt ecps) http://schemas.xmlsoap.org/soap/envelope/t Ss urn:liberty:paos:2003-08t paoss //ecp:RelayStates6 /S:Envelope/S:Header/paos:Request/@responseConsumerURLs> /S:Envelope/S:Header/ecp:Response/@AssertionConsumerServiceURLsb
S:Server
responseConsumerURL from SP and
assertionConsumerServiceURL from IdP do not match
c K sE t t | ƒ i d | | | | _ | | _ | | | _ | _ d S( NR ( R+ R@ t __init__R t identity_provider_urlt _usernamet _password( R R R RG R& R) R ( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyRF ¥ s c C s | i S( N( RH ( R ( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyR& ¯ s c C s
| | _ d S( N( RH ( R t value( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyR& ´ s c C s | i S( N( RI ( R ( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyR) ¹ s c C s
| | _ d S( N( RI ( R RJ ( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyR) ¾ s c K s> | i | i j o | S| i d } | i | | d t | S( Nt locationt
authenticated( t status_codeR3 R= t requestt False( R R; t responset methodR RK ( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyt _handle_http_302_ecp_redirectà s
c C s | | i } | i | ƒ d S( N( t SAML2_HEADER_INDEXt remove( R t saml2_authn_requestt header( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyt _prepare_idp_saml2_requestÌ s
c C s | | j op | i | d | i d | i d t ƒt d ƒ } | h | i d 6| d 6| i d 6| d 6} t i | ƒ ‚ n d S(
sØ Check if consumer URLs issued by SP and IdP are equal.
In the initial SAML2 authn Request issued by a Service Provider
there is a url called ``consumer url``. A trusted Identity Provider
should issue identical url. If the URLs are not equal the federated
authn process should be interrupted and the user should be warned.
:param session: session object to send out HTTP requests.
:type session: keystoneclient.session.Session
:param sp_response_consumer_url: consumer URL issued by a SP
:type sp_response_consumer_url: string
:param idp_sp_response_consumer_url: consumer URL issued by an IdP
:type idp_sp_response_consumer_url: string
t dataR= RL s› Consumer URLs from Service Provider %(service_provider)s %(sp_consumer_url)s and Identity Provider %(identity_provider)s %(idp_consumer_url)s are not equalt service_providert sp_consumer_urlR t idp_consumer_urlN( t postt
SOAP_FAULTt ECP_SP_SAML2_REQUEST_HEADERSRO R R# R R t ValidationError( R R; t sp_response_consumer_urlt idp_sp_response_consumer_urlR ( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyt _check_consumer_urlsÐ s
c C sö | i | i d | i d t ƒ} d | i j o | | _ t Sy t i | i ƒ | _
Wn7 t i j
o( } t d ƒ | } t
i | ƒ ‚ n X| i
i | i d | i ƒ} | i | ƒ | _ | i
i | i d | i ƒ} | i | ƒ | _ t S( sÍ Initial HTTP GET request to the SAML2 protected endpoint.
It's crucial to include HTTP headers indicating that the client is
willing to take advantage of the ECP SAML2 extension and receive data
as the SOAP.
Unlike standard authentication methods in the OpenStack Identity,
the client accesses::
``/v3/OS-FEDERATION/identity_providers/{identity_providers}/
protocols/{protocol}/auth``
After a successful HTTP call the HTTP response should include SAML2
authn request in the XML format.
If a HTTP response contains ``X-Subject-Token`` in the headers and
the response body is a valid JSON assume the user was already
authenticated and Keystone returned a valid unscoped token.
Return True indicating the user was already authenticated.
:param session: a session object to send out HTTP requests.
:type session: keystoneclient.session.Session
R= RL s X-Subject-TokensC SAML2: Error parsing XML returned from Service Provider, reason: %st
namespaces( t getR# t ECP_SP_EMPTY_REQUEST_HEADERSRO R= t authenticated_responseR6 R R
R RU R R R R t xpatht ECP_RELAY_STATEt ECP_SAML2_NAMESPACESR t relay_statet! ECP_SERVICE_PROVIDER_CONSUMER_URLR` ( R R; t sp_responseR R Rj R` ( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyt _send_service_provider_requestô s( c C s | i | i ƒ | i } | i | i d h d d 6d t i | ƒ d | i | i f d t d t ƒ} y t i | i
ƒ | _ Wn7 t i j
o( } t
d ƒ | } t i | ƒ ‚ n X| i i | i d | i ƒ} | i | ƒ | _ | i | | i | i ƒ d
S( sA Present modified SAML2 authn assertion from the Service Provider.R= s text/xmls Content-typeRX t
requests_authRL t logsD SAML2: Error parsing XML returned from Identity Provider, reason: %sRc N( RW RU R\ RG R R R& R) RO R
R t saml2_idp_authn_responseR R R R Rg t ECP_IDP_CONSUMER_URLRi R t idp_response_consumer_urlRb R` ( R R; t idp_saml2_authn_requestt idp_responseR R Rr ( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyt _send_idp_saml2_authn_request$ s(
c
C s{ | i | i d d <| i | i d | i d t i | i ƒ d t d t ƒ} | i | | d d d | i ƒ} | | _ d S( s6 Present SAML2 assertion to the Service Provider.
The assertion is issued by a trusted Identity Provider for the
authenticated user. This function directs the HTTP request to SP
managed URL, for instance: ``https://:/Shibboleth.sso/
SAML2/ECP``.
Upon success the there's a session created and access to the protected
resource is granted. Many implementations of the SP return HTTP 302
status code pointing to the protected URL (``https://:/v3/
OS-FEDERATION/identity_providers/{identity_provider}/protocols/
{protocol_id}/auth`` in this case). Saml2 plugin should point to that
URL again, with HTTP GET method, expecting an unscoped token.
:param session: a session object to send out HTTP requests.
i R= RX RL t redirectRQ t GETN(
Rj Rp R\ Rr R^ R R RO RR Rf ( R R; RP ( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyt+ _send_service_provider_saml2_authn_responseB s c C sU | i | ƒ } | p | i | ƒ | i | ƒ n | i i d | i i ƒ d f S( sG Get unscoped OpenStack token after federated authentication.
This is a multi-step process including multiple HTTP requests.
The federated authentication consists of::
* HTTP GET request to the Identity Service (acting as a Service
Provider). Client utilizes URL::
``/v3/OS-FEDERATION/identity_providers/{identity_provider}/
protocols/saml2/auth``.
It's crucial to include HTTP headers indicating we are expecting
SOAP message in return.
Service Provider should respond with such SOAP message.
This step is handed by a method
``Saml2UnscopedToken_send_service_provider_request()``
* HTTP POST request to the external Identity Provider service with
ECP extension enabled. The content sent is a header removed SOAP
message returned from the Service Provider. It's also worth noting
that ECP extension to the SAML2 doesn't define authentication method.
The most popular is HttpBasicAuth with just user and password.
Other possibilities could be X509 certificates or Kerberos.
Upon successful authentication the user should receive a SAML2
assertion.
This step is handed by a method
``Saml2UnscopedToken_send_idp_saml2_authn_request(session)``
* HTTP POST request again to the Service Provider. The body of the
request includes SAML2 assertion issued by a trusted Identity
Provider. The request should be sent to the Service Provider
consumer url specified in the SAML2 assertion.
Providing the authentication was successful and both Service Provider
and Identity Providers are trusted to each other, the Service
Provider will issue an unscoped token with a list of groups the
federated user is a member of.
This step is handed by a method
``Saml2UnscopedToken_send_service_provider_saml2_authn_response()``
Unscoped token example::
{
"token": {
"methods": [
"saml2"
],
"user": {
"id": "username%40example.com",
"name": "username@example.com",
"OS-FEDERATION": {
"identity_provider": "ACME",
"protocol": "saml2",
"groups": [
{"id": "abc123"},
{"id": "bcd234"}
]
}
}
}
}
:param session : a session object to send out HTTP requests.
:type session: keystoneclient.session.Session
:returns: (token, token_json)
s X-Subject-Tokent token( Rm Ru Rx Rf R= t json( R R; t saml_authenticated( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyt _get_unscoped_tokene s C
c K s% | i | ƒ \ } } t i | | S( s. Authenticate via SAML2 protocol and retrieve unscoped token.
This is a multi-step process where a client does federated authn
receives an unscoped token.
Federated authentication utilizing SAML2 Enhanced Client or Proxy
extension. See ``Saml2UnscopedToken_get_unscoped_token()``
for more information on that step.
Upon successful authentication and assertion mapping an
unscoped token is returned and stored within the plugin object for
further use.
:param session : a session object to send out HTTP requests.
:type session: keystoneclient.session.Session
:return: an object with scoped token's id and unscoped token json
included.
:rtype: :py:class:`keystoneclient.access.AccessInfoV3`
( R| R t AccessInfoV3( R R; R Ry t
token_json( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyt get_auth_ref¯ s ( R1 R2 t __doc__R9 t _auth_method_classRS Re R^ Ri Rh Rk Rq R] RF R7 R& t setterR) RR RW Rb Rm Ru Rx R| R ( ( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyR@ X s: #
$ 0 # Jt ADFSUnscopedTokenc B s e Z d Z e Z d Z h d d 6Z h d d 6Z h d d 6d d 6d d
6Z h d d 6d d 6Z d
Z
d „ Z e d „ ƒ Z
e
i d „ ƒ Z
e d „ ƒ Z e i d „ ƒ Z e d „ ƒ Z d „ Z d d „ Z d „ Z d „ Z d „ Z d „ Z d „ Z d „ Z d „ Z RS( s¼ Authentication plugin for Microsoft ADFS2.0 IdPs.
:param auth_url: URL of the Identity Service
:type auth_url: string
:param identity_provider: name of the Identity Provider the client will
authenticate against. This parameter will be used
to build a dynamic URL used to obtain unscoped
OpenStack token.
:type identity_provider: string
:param identity_provider_url: An Identity Provider URL, where the SAML2
authentication request will be sent.
:type identity_provider_url: string
:param service_provider_endpoint: Endpoint where an assertion is being
sent, for instance: ``https://host.domain/Shibboleth.sso/ADFS``
:type service_provider_endpoint: string
:param username: User's login
:type username: string
:param password: User's password
:type password: string
ix s# application/soap+xml; charset=utf-8s Content-Types! application/x-www-form-urlencodeds' http://www.w3.org/2003/05/soap-envelopet ss$ http://www.w3.org/2005/08/addressingt asR http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsdt us0 http://docs.oasis-open.org/ws-sx/ws-trust/200512t tsZ /s:Envelope/s:Body/t:RequestSecurityTokenResponseCollection/t:RequestSecurityTokenResponsec K sN t t | ƒ i d | | | | _ | | _ | | _ | | | _ | _ d S( NR ( R+ Rƒ RF R RG t service_provider_endpointRH RI ( R R R RG Rˆ R& R) R ( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyRF û s
c C s | i S( N( RH ( R ( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyR& s c C s
| | _ d S( N( RH ( R RJ ( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyR& s c C s | i S( N( RI ( R ( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyR)
s c C s
| | _ d S( N( RI ( R RJ ( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyR) s c C s8 t t | ƒ i ƒ } | i t i d d d ƒg ƒ | S( Ns service-provider-endpointR$ s Service Provider's Endpoint( R+ Rƒ R, R- R R. ( R/ R0 ( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyR, s
c C s7 y t | i ƒ SWn t j
o n Xt | i i ƒ S( sÚ Check if cookie jar is not empty.
keystoneclient.session.Session object doesn't have a cookies attribute.
We should then try fetching cookies from the underlying
requests.Session object. If that fails too, there is something wrong
and let Python raise the AttributeError.
:param session
:returns: True if cookie jar is nonempty, False otherwise
:raises AttributeError: in case cookies are not find anywhere
( t boolt cookiest AttributeErrorR; ( R R; ( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyt _cookies! s
s %Y-%m-%dT%H:%M:%S.%fZc C sV t i i ƒ } | t i d | i ƒ } g } | | f D] } | | i | ƒ q9 ~ S( sò Calculate created and expires datetime objects.
The method is going to be used for building ADFS Request Security
Token message. Time interval between ``created`` and ``expires``
dates is now static and equals to 120 seconds. ADFS security tokens
should not be live too long, as currently ``keystoneclient``
doesn't have mechanisms for reusing such tokens (every time ADFS authn
method is called, keystoneclient will login with the ADFS instance).
:param fmt: Datetime format for specifying string format of a date.
It should not be changed if the method is going to be used
for building the ADFS security token request.
:type fmt: string
t seconds( t datetimet utcnowt timedeltat DEFAULT_ADFS_TOKEN_EXPIRATIONt strftime( R t fmtt date_createdt date_expirest _[1]t _time( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyt _token_dates5 s
c C sÙ h d d 6} h d d 6} h d d 6} h d d 6} t i d d
| i ƒ} t i | d ƒ } t i | d ƒ } | i d
d ƒ d | _ t i | d ƒ } d t i ƒ i | _ t i | d ƒ } t i | d ƒ }
d |
_ t i | d ƒ } | i d
d ƒ t i | d d
| ƒ} | i d
d ƒ t i | d ƒ }
|
i d d ƒ t i |
d ƒ } t i |
d ƒ } | i ƒ \ | _ | _ t i | d ƒ } | i d d t i ƒ i ƒ t i | d ƒ } t i | d d! d" ƒ} t i | d# ƒ } t i | d$ d
| ƒ} t i | d% d
| ƒ} t i | d& d
| ƒ} t i | d ƒ } t i | d' ƒ } d( | _ t i | d) ƒ } d* | _ t i | d+ ƒ } d, | _ | i
| _ | i | _ | i | _ | i
| _ | | _ d- S(. s‰ Build the ADFS Request Security Token SOAP message.
Some values like username or password are inserted in the request.
sQ http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsdt os0 http://docs.oasis-open.org/ws-sx/ws-trust/200512t trusts, http://schemas.xmlsoap.org/ws/2004/09/policyt wsps$ http://www.w3.org/2005/08/addressingt wsas1 {http://www.w3.org/2003/05/soap-envelope}Envelopet nsmaps/ {http://www.w3.org/2003/05/soap-envelope}Headers, {http://www.w3.org/2005/08/addressing}Actions7 {http://www.w3.org/2003/05/soap-envelope}mustUnderstandt 1s: http://docs.oasis-open.org/ws-sx/ws-trust/200512/RST/Issues/ {http://www.w3.org/2005/08/addressing}MessageIDs urn:uuid:s- {http://www.w3.org/2005/08/addressing}ReplyTos- {http://www.w3.org/2005/08/addressing}Addresss. http://www.w3.org/2005/08/addressing/anonymouss( {http://www.w3.org/2005/08/addressing}Tos[ {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}Securitys] {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd}TimestampsV {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd}Idt _0s[ {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd}Createds[ {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd}Expiress` {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}UsernameTokensU {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd}us uuid-%s-1s[ {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}Usernames[ {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}Passwordt Types_ http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordTexts- {http://www.w3.org/2003/05/soap-envelope}BodysF {http://docs.oasis-open.org/ws-sx/ws-trust/200512}RequestSecurityTokens7 {http://schemas.xmlsoap.org/ws/2004/09/policy}AppliesTos7 {http://www.w3.org/2005/08/addressing}EndpointReferences9 {http://docs.oasis-open.org/ws-sx/ws-trust/200512}KeyTypes7 http://docs.oasis-open.org/ws-sx/ws-trust/200512/Bearers= {http://docs.oasis-open.org/ws-sx/ws-trust/200512}RequestTypes6 http://docs.oasis-open.org/ws-sx/ws-trust/200512/Issues; {http://docs.oasis-open.org/ws-sx/ws-trust/200512}TokenTypes% urn:oasis:names:tc:SAML:1.0:assertionN( R t Elementt
NAMESPACESt
SubElementt sett textt uuidt uuid4t hexR˜ R& R) RG Rˆ t prepared_request( R t WSS_SECURITY_NAMESPACEt TRUST_NAMESPACEt
WSP_NAMESPACEt
WSA_NAMESPACEt rootRV t actiont messageIDt replyIDt addresst tot securityt timestampt createdt expirest
usernametokenR& R) t bodyt request_security_tokent
applies_tot endpoint_referencet wsa_addresst keytypet request_typet
token_type( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyt _prepare_adfs_requestK s®
c
s ‡ f d † } ˆ i ˆ i ƒ } y. | i d ˆ i d ˆ i d | d t ƒ } Wn3 t i j
o$ } | | ƒ } t i | ƒ ‚ n Xt d ƒ } ˆ i
| i | ƒ ˆ _ d S( sl Send ADFS Security token to the ADFS server.
Store the result in the instance attribute and raise an exception in
case the response is not valid XML data.
If a user cannot authenticate due to providing bad credentials, the
ADFS2.0 server will return a HTTP 500 response and a XML Fault message.
If ``exceptions.InternalServerError`` is caught, the method tries to
parse the XML response.
If parsing is unsuccessful, an ``exceptions.AuthorizationFailure`` is
raised with a reason from the XML fault. Otherwise an original
``exceptions.InternalServerError`` is re-raised.
:param session : a session object to send out HTTP requests.
:type session: keystoneclient.session.Session
:raises keystoneclient.exceptions.AuthorizationFailure: when HTTP
response from the ADFS server is not a valid XML ADFS security
token.
:raises keystoneclient.exceptions.InternalServerError: If response
status code is HTTP 500 and the response XML cannot be
recognized.
c sv d } | i i } y; ˆ i | ƒ i | d ˆ i ƒ} ˆ i | ƒ } | i SWn" t t i f j
o
| ‚ n Xd S( Ns3 /s:Envelope/s:Body/s:Fault/s:Code/s:Subcode/s:ValueRc (
RP R R Rg R¢ R R¥ R
R R ( R Rg R t obj( R ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyt _get_failureì s R" R= RX RL sF Error parsing XML returned from the ADFS Identity Provider, reason: %sN(
R R© R\ RG t HEADER_SOAPRO R t InternalServerErrorR R R R t
adfs_token( R R; RÃ Rº RP R t reasonR ( ( R sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyt _get_adfs_security_tokenÓ s c C sq | i i | i d | i ƒ} | i | ƒ } | i | ƒ } | i d d ƒ } t i i | ƒ } d | | _
d S( s) Prepare ADFS Security Token to be sent to the Service Provider.
The method works as follows:
* Extract SAML2 assertion from the ADFS Security Token.
* Replace namespaces
* urlencode assertion
* concatenate static string with the encoded assertion
Rc s0 http://docs.oasis-open.org/ws-sx/ws-trust/200512s+ http://schemas.xmlsoap.org/ws/2005/02/trusts wa=wsignin1.0&wresult=N( RÆ Rg t ADFS_ASSERTION_XPATHt ADFS_TOKEN_NAMESPACESR R t replaceR t parset quotet encoded_assertion( R t assertionRÎ ( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyt _prepare_sp_request s
c C s5 | i d | i d | i d | i d t d t ƒ d S( s! Send prepared assertion to a service provider.
As the assertion doesn't contain a protected resource, the value from
the ``location`` header is not valid and we should not let the Session
object get redirected there. The aim of this call is to get a cookie in
the response which is required for entering a protected endpoint.
:param session : a session object to send out HTTP requests.
:type session: keystoneclient.session.Session
:raises: Corresponding HTTP error exception
R" RX R= Rv RL N( R\ Rˆ RÎ t
HEADER_X_FORMRO ( R R; ( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyt# _send_assertion_to_service_provider" s c C sN | i | ƒ t j o t i t d ƒ ƒ ‚ n | i | i d t ƒ| _ d S( s Access protected endpoint and fetch unscoped token.
After federated authentication workflow a protected endpoint should be
accessible with the session object. The access is granted basing on the
cookies stored within the session object. If, for some reason no
cookies are present (quantity test) it means something went wrong and
user will not be able to fetch an unscoped token. In that case an
``exceptions.AuthorizationFailure` exception is raised and no HTTP call
is even made.
:param session : a session object to send out HTTP requests.
:type session: keystoneclient.session.Session
:raises keystoneclient.exceptions.AuthorizationFailure: in case session
object has empty cookie jar.
sw Session object doesn't contain a cookie, therefore you are not allowed to enter the Identity Provider's protected area.RL N( RΠRO R R R Rd R# Rf ( R R; ( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyt _access_service_provider4 s
c G s• | i ƒ | i | ƒ | i ƒ | i | ƒ | i | ƒ y% | i i d | i i ƒ d f SWn. t t f j
o t
i d | i ƒ ‚ n Xd S( sÌ Retrieve unscoped token after authentcation with ADFS server.
This is a multistep process::
* Prepare ADFS Request Securty Token -
build a etree.XML object filling certain attributes with proper user
credentials, created/expires dates (ticket is be valid for 120 seconds
as currently we don't handle reusing ADFS issued security tokens) .
Step handled by ``ADFSUnscopedToken._prepare_adfs_request()`` method.
* Send ADFS Security token to the ADFS server. Step handled by
``ADFSUnscopedToken._get_adfs_security_token()`` method.
* Receive and parse security token, extract actual SAML assertion and
prepare a request addressed for the Service Provider endpoint.
This also includes changing namespaces in the XML document. Step
handled by ``ADFSUnscopedToken._prepare_sp_request()`` method.
* Send prepared assertion to the Service Provider endpoint. Usually
the server will respond with HTTP 301 code which should be ignored as
the 'location' header doesn't contain protected area. The goal of this
operation is fetching the session cookie which later allows for
accessing protected URL endpoints. Step handed by
``ADFSUnscopedToken._send_assertion_to_service_provider()`` method.
* Once the session cookie is issued, the protected endpoint can be
accessed and an unscoped token can be retrieved. Step handled by
``ADFSUnscopedToken._access_service_provider()`` method.
:param session : a session object to send out HTTP requests.
:type session: keystoneclient.session.Session
:returns: (Unscoped federated token, token JSON body)
s X-Subject-TokenRy RP N( RÁ RÈ RÐ RÒ RÓ Rf R= Rz t KeyErrort
ValueErrorR t InvalidResponse( R R; R ( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyR| N s $
c K s% | i | ƒ \ } } t i | | S( N( R| R R} ( R R; R Ry R~ ( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyR s ( R1 R2 R€ R9 R R‘ RÄ RÑ R¢ RÊ RÉ RF R7 R& R‚ R) R8 R, RŒ R˜ RÁ RÈ RÐ RÒ RÓ R| R ( ( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyRƒ É s8
ˆ 6 1t Saml2ScopedTokenMethodc B s e Z d Z d „ Z RS( R c K s: t t | ƒ i | | | | } | \ } } | i | f S( s5 Build and return request body for token scoping step.( R+ R× R> t _method_name( R R; R< R= R R‡ t
_token_methodRy ( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyR> ‡ s ( R1 R2 RØ R> ( ( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyR× „ s t Saml2ScopedTokenc B s e Z d Z e Z d „ Z RS( s' Class for scoping unscoped saml2 token.c K sM t t | ƒ i | | | | i p | i p t i t d ƒ ƒ ‚ n d S( Ns$ Neither project nor domain specified( R+ RÚ RF t
project_idt domain_idR R_ R ( R R Ry R ( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyRF • s ( R1 R2 R€ R× R RF ( ( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyRÚ s ( RŽ R¦ t lxmlR t oslo_configR t six.movesR t keystoneclientR t keystoneclient.auth.identityR R t keystoneclient.i18nR t AuthConstructorR t
AuthMethodR9 R@ Rƒ t TokenMethodR× t TokenRÚ ( ( ( sS /tmp/pip-build-cD3xZi/python-keystoneclient/keystoneclient/contrib/auth/v3/saml2.pyt
s 6ÿ rÿ ¼