Gemfury

360core / pysaml2 python

Repository URL to install this package:
Details
pysaml2 / doc / _build / doctrees / examples / sp.doctree
cdocutils.nodes
document
q)q}q(U	nametypesq}q(Xhow it worksqNXsetupqNX7an extremly simple example of a saml2 service provider.qNXrepoze configurationq	NXmiddleware responsibilitiesq
KX
example_spqKXthe applicationqNXsp configurationq
NuUsubstitution_defsq}qUparse_messagesq]qcdocutils.nodes
system_message
q)q}q(U	rawsourceqUUparentqcdocutils.nodes
section
q)q}q(hUU
referencedqKhh)q}q(hUhhUsourceqcdocutils.nodes
reprunicode
qX</home/lgs/proyectos/yaco/pysaml2/pysaml2/doc/examples/sp.rstqq }q!bUexpect_referenced_by_nameq"}q#hcdocutils.nodes
target
q$)q%}q&(hX.. _example_sp:hhhh Utagnameq'Utargetq(U
attributesq)}q*(Uidsq+]Ubackrefsq,]Udupnamesq-]Uclassesq.]Unamesq/]Urefidq0U
example-spq1uUlineq2KUdocumentq3hUchildrenq4]ubsh'Usectionq5h)}q6(h-]h.]h,]h+]q7(U6an-extremly-simple-example-of-a-saml2-service-providerq8h1eh/]q9(hheuh2Kh3hUexpect_referenced_by_idq:}q;h1h%sh4]q<(cdocutils.nodes
title
q=)q>}q?(hX7An extremly simple example of a SAML2 service provider.q@hhhh h'UtitleqAh)}qB(h-]h.]h,]h+]h/]uh2Kh3hh4]qCcdocutils.nodes
Text
qDX7An extremly simple example of a SAML2 service provider.qEqF}qG(hh@hh>ubaubh)qH}qI(hUhhhh h'h5h)}qJ(h-]h.]h,]h+]qKUhow-it-worksqLah/]qMhauh2Kh3hh4]qN(h=)qO}qP(hXHow it worksqQhhHhh h'hAh)}qR(h-]h.]h,]h+]h/]uh2Kh3hh4]qShDXHow it worksqTqU}qV(hhQhhOubaubcdocutils.nodes
paragraph
qW)qX}qY(hXÍA SP works with authentication and possibly attribute aggregation.
Both of these functions can be seen as parts of the normal Repoze.who
setup. Namely the Challenger, Identifier and MetadataProvider parts.qZhhHhh h'U	paragraphq[h)}q\(h-]h.]h,]h+]h/]uh2K	h3hh4]q]hDXÍA SP works with authentication and possibly attribute aggregation.
Both of these functions can be seen as parts of the normal Repoze.who
setup. Namely the Challenger, Identifier and MetadataProvider parts.q^q_}q`(hhZhhXubaubhW)qa}qb(hXNormal for Repoze.who Identifier and MetadataProvider plugins are that
they place information in environment variables. The convention is to place
identity information in environ["repoze.who.identity"].
This is a dictionary with keys like 'login', and 'repoze.who.userid'.qchhHhh h'h[h)}qd(h-]h.]h,]h+]h/]uh2K
h3hh4]qehDXNormal for Repoze.who Identifier and MetadataProvider plugins are that
they place information in environment variables. The convention is to place
identity information in environ["repoze.who.identity"].
This is a dictionary with keys like 'login', and 'repoze.who.userid'.qfqg}qh(hhchhaubaubhW)qi}qj(hXçThe SP follows this pattern and places the information gathered from
the IdP that handled the authentication and possible extra information
received from attribute authorities in the above mentioned dictionary under
the key 'user'.qkhhHhh h'h[h)}ql(h-]h.]h,]h+]h/]uh2Kh3hh4]qmhDXçThe SP follows this pattern and places the information gathered from
the IdP that handled the authentication and possible extra information
received from attribute authorities in the above mentioned dictionary under
the key 'user'.qnqo}qp(hhkhhiubaubhW)qq}qr(hXSo in environ["repoze.who.identity"] you will find a dictionary with
attributes and values, the attribute names used depends on what's returned
from the IdP/AA. If there exists both a name and a friendly name, for
instance, the friendly name is used as the key.qshhHhh h'h[h)}qt(h-]h.]h,]h+]h/]uh2Kh3hh4]quhDXSo in environ["repoze.who.identity"] you will find a dictionary with
attributes and values, the attribute names used depends on what's returned
from the IdP/AA. If there exists both a name and a friendly name, for
instance, the friendly name is used as the key.qvqw}qx(hhshhqubaubeubh)qy}qz(hUhhhh h'h5h)}q{(h-]h.]h,]h+]q|Usetupq}ah/]q~hauh2Kh3hh4]q(h=)q}q(hXSetupqhhyhh h'hAh)}q(h-]h.]h,]h+]h/]uh2Kh3hh4]qhDXSetupqq}q(hhhhubaubhW)q}q(hX\I you look in the example/sp directory of the distribution you will see
the necessary files:qhhyhh h'h[h)}q(h-]h.]h,]h+]h/]uh2Kh3hh4]qhDX\I you look in the example/sp directory of the distribution you will see
the necessary files:qq}q(hhhhubaubcdocutils.nodes
definition_list
q)q}q(hUhhyhh h'Udefinition_listqh)}q(h-]h.]h,]h+]h/]uh2Nh3hh4]q(cdocutils.nodes
definition_list_item
q)q}q(hX}application.py
which is the web application. In this case it will just print the
information provided by the IdP in a table.
hhhh h'Udefinition_list_itemqh)}q(h-]h.]h,]h+]h/]uh2K$h4]q(cdocutils.nodes
term
q)q}q(hUh)}q(h-]h.]h,]h+]h/]uhhh4]q hDXapplication.pyq¡q¢}q£(hXapplication.pyq¤hhubah'Utermq¥ubcdocutils.nodes
definition
q¦)q§}q¨(hUh)}q©(h-]h.]h,]h+]h/]uhhh4]qªhW)q«}q¬(hXmwhich is the web application. In this case it will just print the
information provided by the IdP in a table.qhh§hh h'h[h)}q®(h-]h.]h,]h+]h/]uh2K#h4]q¯hDXmwhich is the web application. In this case it will just print the
information provided by the IdP in a table.q°q±}q²(hhhh«ubaubah'U
definitionq³ubeubh)q´}qµ(hX!sp_conf.py
The SPs configuration
hhhh h'hh)}q¶(h-]h.]h,]h+]h/]uh2K'h3hh4]q·(h)q¸}q¹(hUh)}qº(h-]h.]h,]h+]h/]uhh´h4]q»hDX
sp_conf.pyq¼q½}q¾(hX
sp_conf.pyq¿hh¸ubah'h¥ubh¦)qÀ}qÁ(hUh)}qÂ(h-]h.]h,]h+]h/]uhh´h4]qÃhW)qÄ}qÅ(hXThe SPs configurationqÆhhÀhh h'h[h)}qÇ(h-]h.]h,]h+]h/]uh2K'h4]qÈhDXThe SPs configurationqɅqÊ}qË(hhÆhhÄubaubah'h³ubeubh)qÌ}qÍ(hX*who.ini
The repoze.who configuration file
hhhh h'hh)}qÎ(h-]h.]h,]h+]h/]uh2K*h3hh4]qÏ(h)qÐ}qÑ(hUh)}qÒ(h-]h.]h,]h+]h/]uhhÌh4]qÓhDXwho.iniqԅqÕ}qÖ(hXwho.iniq×hhÐubah'h¥ubh¦)qØ}qÙ(hUh)}qÚ(h-]h.]h,]h+]h/]uhhÌh4]qÛhW)qÜ}qÝ(hX!The repoze.who configuration fileqÞhhØhh h'h[h)}qß(h-]h.]h,]h+]h/]uh2K*h4]qàhDX!The repoze.who configuration fileqᅁqâ}qã(hhÞhhÜubaubah'h³ubeubeubhW)qä}qå(hX{And then there are two files with certificates, mykey.pem with the private
certificate and mycert.pem with the public part.qæhhyhh h'h[h)}qç(h-]h.]h,]h+]h/]uh2K,h3hh4]qèhDX{And then there are two files with certificates, mykey.pem with the private
certificate and mycert.pem with the public part.q酁qê}që(hhæhhäubaubhW)qì}qí(hX#I'll go through these step by step.qîhhyhh h'h[h)}qï(h-]h.]h,]h+]h/]uh2K/h3hh4]qðhDX#I'll go through these step by step.qñqò}qó(hhîhhìubaubeubh)qô}qõ(hUhKhhhh h'h5h)}qö(h-]q÷Xthe applicationqøah.]h,]h+]qùUthe-applicationqúah/]uh2K2h3hh4]qû(h=)qü}qý(hXThe applicationqþhhôhh h'hAh)}qÿ(h-]h.]h,]h+]h/]uh2K2h3hh4]rhDXThe applicationrr}r(hhþhhüubaubhW)r}r(hX[Build to use the wsgiref's simple_server, which is fine for testing but
not for production.rhhôhh h'h[h)}r(h-]h.]h,]h+]h/]uh2K4h3hh4]rhDX[Build to use the wsgiref's simple_server, which is fine for testing but
not for production.r	r
}r(hjhjubaubeubh)r}r
(hUhhhh h'h5h)}r(h-]h.]h,]h+]rUsp-configurationrah/]rh
auh2K9h3hh4]r(h=)r}r(hXSP configurationrhjhh h'hAh)}r(h-]h.]h,]h+]h/]uh2K9h3hh4]rhDXSP configurationrr}r(hjhjubaubhW)r}r(hXThe configuration is written as described in :ref:`howto_config`. It means among other
things that it's easily testable as to the correct syntax.hjhh h'h[h)}r(h-]h.]h,]h+]h/]uh2K;h3hh4]r(hDX-The configuration is written as described in rr }r!(hX-The configuration is written as described in hjubcsphinx.addnodes
pending_xref
r")r#}r$(hX:ref:`howto_config`r%hjh'Upending_xrefr&h)}r'(UreftypeXrefUrefwarnr(U	reftargetr)Xhowto_configU	refdomainXstdr*h+]h,]Urefexplicith-]h.]h/]Urefdocr+Uexamples/spr,uh2K;h4]r-cdocutils.nodes
emphasis
r.)r/}r0(hj%h)}r1(h-]h.]r2(Uxrefr3j*Xstd-refr4eh,]h+]h/]uhj#h4]r5hDXhowto_configr6r7}r8(hUhj/ubah'Uemphasisr9ubaubhDXQ. It means among other
things that it's easily testable as to the correct syntax.r:r;}r<(hXQ. It means among other
things that it's easily testable as to the correct syntax.hjubeubhW)r=}r>(hX]You can see the whole file in example/sp/sp_conf.py, here I will go through
it line by line::hjhh h'h[h)}r?(h-]h.]h,]h+]h/]uh2K>h3hh4]r@hDX\You can see the whole file in example/sp/sp_conf.py, here I will go through
it line by line:rArB}rC(hX\You can see the whole file in example/sp/sp_conf.py, here I will go through
it line by line:hj=ubaubcdocutils.nodes
literal_block
rD)rE}rF(hX"service": ["sp"],hjhh h'U
literal_blockrGh)}rH(U	xml:spacerIUpreserverJh+]h,]h-]h.]h/]uh2KAh3hh4]rKhDX"service": ["sp"],rLrM}rN(hUhjEubaubhW)rO}rP(hXGTells the software what type of services the software are suppost to
supply. It is used to check for the
completeness of the configuration and also when constructing metadata from
the configuration. More about that later. Allowed values are: "sp"
(service provider), "idp" (identity provider) and "aa" (attribute authority).
::hjhh h'h[h)}rQ(h-]h.]h,]h+]h/]uh2KCh3hh4]rRhDXDTells the software what type of services the software are suppost to
supply. It is used to check for the
completeness of the configuration and also when constructing metadata from
the configuration. More about that later. Allowed values are: "sp"
(service provider), "idp" (identity provider) and "aa" (attribute authority).rSrT}rU(hXDTells the software what type of services the software are suppost to
supply. It is used to check for the
completeness of the configuration and also when constructing metadata from
the configuration. More about that later. Allowed values are: "sp"
(service provider), "idp" (identity provider) and "aa" (attribute authority).hjOubaubjD)rV}rW(hXX"entityid" : "urn:mace:example.com:saml:sp",
"service_url" : "http://example.com:8087/",hjhh h'jGh)}rX(jIjJh+]h,]h-]h.]h/]uh2KJh3hh4]rYhDXX"entityid" : "urn:mace:example.com:saml:sp",
"service_url" : "http://example.com:8087/",rZr[}r\(hUhjVubaubhW)r]}r^(hX<The ID of the entity and the URL on which it is listening.::r_hjhh h'h[h)}r`(h-]h.]h,]h+]h/]uh2KMh3hh4]rahDX;The ID of the entity and the URL on which it is listening.:rbrc}rd(hX;The ID of the entity and the URL on which it is listening.:hj]ubaubjD)re}rf(hX;"idp_url" : "https://example.com/saml2/idp/SSOService.php",hjhh h'jGh)}rg(jIjJh+]h,]h-]h.]h/]uh2KOh3hh4]rhhDX;"idp_url" : "https://example.com/saml2/idp/SSOService.php",rirj}rk(hUhjeubaubhW)rl}rm(hXÏSince this is a very simple SP it only need to know about one IdP, therefor there
is really no need for a metadata file or a WAYF-function or anything like that.
It needs the URL of the IdP and that's all.::hjhh h'h[h)}rn(h-]h.]h,]h+]h/]uh2KQh3hh4]rohDXÎSince this is a very simple SP it only need to know about one IdP, therefor there
is really no need for a metadata file or a WAYF-function or anything like that.
It needs the URL of the IdP and that's all.:rprq}rr(hXÎSince this is a very simple SP it only need to know about one IdP, therefor there
is really no need for a metadata file or a WAYF-function or anything like that.
It needs the URL of the IdP and that's all.:hjlubaubjD)rs}rt(hX"my_name" : "My first SP",hjhh h'jGh)}ru(jIjJh+]h,]h-]h.]h/]uh2KUh3hh4]rvhDX"my_name" : "My first SP",rwrx}ry(hUhjsubaubhW)rz}r{(hXFThis is just for informal purposes, not really needed but nice to do::r|hjhh h'h[h)}r}(h-]h.]h,]h+]h/]uh2KWh3hh4]r~hDXEThis is just for informal purposes, not really needed but nice to do:rr}r(hXEThis is just for informal purposes, not really needed but nice to do:hjzubaubjD)r}r(hX"debug" : 1,hjhh h'jGh)}r(jIjJh+]h,]h-]h.]h/]uh2KYh3hh4]rhDX"debug" : 1,rr}r(hUhjubaubhW)r}r(hXwWell, at this point in time you'd really like to have as much information
as possible as to what's going on, right ? ::hjhh h'h[h)}r(h-]h.]h,]h+]h/]uh2K[h3hh4]rhDXtWell, at this point in time you'd really like to have as much information
as possible as to what's going on, right ?rr}r(hXtWell, at this point in time you'd really like to have as much information
as possible as to what's going on, right ?hjubaubjD)r}r(hX9"key_file" : "./mykey.pem",
"cert_file" : "./mycert.pem",hjhh h'jGh)}r(jIjJh+]h,]h-]h.]h/]uh2K^h3hh4]rhDX9"key_file" : "./mykey.pem",
"cert_file" : "./mycert.pem",rr}r(hUhjubaubhW)r}r(hXThe necessary certificates.::rhjhh h'h[h)}r(h-]h.]h,]h+]h/]uh2Kah3hh4]rhDXThe necessary certificates.:rr}r(hXThe necessary certificates.:hjubaubjD)r}r (hX+"xmlsec_binary" : "/opt/local/bin/xmlsec1",hjhh h'jGh)}r¡(jIjJh+]h,]h-]h.]h/]uh2Kch3hh4]r¢hDX+"xmlsec_binary" : "/opt/local/bin/xmlsec1",r£r¤}r¥(hUhjubaubhW)r¦}r§(hXRight now the software is built to use xmlsec binaries and not the python
xmlsec package. There are reasons for this but I won't go into them here.::hjhh h'h[h)}r¨(h-]h.]h,]h+]h/]uh2Keh3hh4]r©hDXRight now the software is built to use xmlsec binaries and not the python
xmlsec package. There are reasons for this but I won't go into them here.:rªr«}r¬(hXRight now the software is built to use xmlsec binaries and not the python
xmlsec package. There are reasons for this but I won't go into them here.:hj¦ubaubjD)r}r®(hXe"organization": {
    "name": "Example Co",
    #display_name
    "url":"http://www.example.com/",
},hjhh h'jGh)}r¯(jIjJh+]h,]h-]h.]h/]uh2Khh3hh4]r°hDXe"organization": {
    "name": "Example Co",
    #display_name
    "url":"http://www.example.com/",
},r±r²}r³(hUhjubaubhW)r´}rµ(hX_Information about the organization that is behind this SP, only used when
building metadata. ::hjhh h'h[h)}r¶(h-]h.]h,]h+]h/]uh2Knh3hh4]r·hDX\Information about the organization that is behind this SP, only used when
building metadata.r¸r¹}rº(hX\Information about the organization that is behind this SP, only used when
building metadata.hj´ubaubjD)r»}r¼(hX¦"contact": [{
    "given_name":"John",
    "sur_name": "Smith",
    "email_address": "john.smith@example.com",
    #contact_type
    #company
    #telephone_number
}]hjhh h'jGh)}r½(jIjJh+]h,]h-]h.]h/]uh2Kqh3hh4]r¾hDX¦"contact": [{
    "given_name":"John",
    "sur_name": "Smith",
    "email_address": "john.smith@example.com",
    #contact_type
    #company
    #telephone_number
}]r¿rÀ}rÁ(hUhj»ubaubhW)rÂ}rÃ(hXWAnother piece of information that only is matters if you build and distribute
metadata.rÄhjhh h'h[h)}rÅ(h-]h.]h,]h+]h/]uh2Kzh3hh4]rÆhDXWAnother piece of information that only is matters if you build and distribute
metadata.rÇrÈ}rÉ(hjÄhjÂubaubhW)rÊ}rË(hX\So, now to that part. In order to allow the IdP to talk to you you may have
to provide the one running the IdP with a metadata file.
If you have a SP configuration file similar to the one I've walked you
through here, but with your information. You can make the metadata file
by running the make_metadata script you can find in the tools directory.rÌhjhh h'h[h)}rÍ(h-]h.]h,]h+]h/]uh2K}h3hh4]rÎhDX\So, now to that part. In order to allow the IdP to talk to you you may have
to provide the one running the IdP with a metadata file.
If you have a SP configuration file similar to the one I've walked you
through here, but with your information. You can make the metadata file
by running the make_metadata script you can find in the tools directory.rÏrÐ}rÑ(hjÌhjÊubaubhW)rÒ}rÓ(hXCChange directory to where you have the configuration file and do ::rÔhjhh h'h[h)}rÕ(h-]h.]h,]h+]h/]uh2Kh3hh4]rÖhDX@Change directory to where you have the configuration file and dor×rØ}rÙ(hX@Change directory to where you have the configuration file and dohjÒubaubjD)rÚ}rÛ(hX*make_metadata.py sp_conf.py > metadata.xmlhjhh h'jGh)}rÜ(jIjJh+]h,]h-]h.]h/]uh2Kh3hh4]rÝhDX*make_metadata.py sp_conf.py > metadata.xmlrÞrß}rà(hUhjÚubaubeubh)rá}râ(hUhhhh h'h5h)}rã(h-]h.]h,]h+]räUrepoze-configurationråah/]ræh	auh2Kh3hh4]rç(h=)rè}ré(hXRepoze configurationrêhjáhh h'hAh)}rë(h-]h.]h,]h+]h/]uh2Kh3hh4]rìhDXRepoze configurationrírî}rï(hjêhjèubaubhW)rð}rñ(hX¶I'm not going through the INI file format here. You should read
`Middleware Responsibilities <http://static.repoze.org/whodocs/narr.html>`_
to get a good introduction to the concept.hjáhh h'h[h)}rò(h-]h.]h,]h+]h/]uh2Kh3hh4]ró(hDX@I'm not going through the INI file format here. You should read
rôrõ}rö(hX@I'm not going through the INI file format here. You should read
hjðubcdocutils.nodes
reference
r÷)rø}rù(hXK`Middleware Responsibilities <http://static.repoze.org/whodocs/narr.html>`_h)}rú(UnameXMiddleware ResponsibilitiesUrefurirûX*http://static.repoze.org/whodocs/narr.htmlrüh+]h,]h-]h.]h/]uhjðh4]rýhDXMiddleware Responsibilitiesrþrÿ}r(hUhjøubah'U	referencerubh$)r}r(hX- <http://static.repoze.org/whodocs/narr.html>h)}r(Urefurijüh+]rUmiddleware-responsibilitiesrah,]h-]h.]h/]rh
auhjðh4]h'h(ubhDX+
to get a good introduction to the concept.rr	}r
(hX+
to get a good introduction to the concept.hjðubeubhW)r}r(hXyThe configuration of the pysaml2 part in the applications middleware are
first the special module configuration, namely::hjáhh h'h[h)}r
(h-]h.]h,]h+]h/]uh2Kh3hh4]rhDXxThe configuration of the pysaml2 part in the applications middleware are
first the special module configuration, namely:rr}r(hXxThe configuration of the pysaml2 part in the applications middleware are
first the special module configuration, namely:hjubaubjD)r}r(hX[plugin:saml2auth]
use = s2repoze.plugins.sp:make_plugin
saml_conf = sp_conf.py
rememberer_name = auth_tkt
debug = 1
path_logout = .*/logout.*hjáhh h'jGh)}r(jIjJh+]h,]h-]h.]h/]uh2Kh3hh4]rhDX[plugin:saml2auth]
use = s2repoze.plugins.sp:make_plugin
saml_conf = sp_conf.py
rememberer_name = auth_tkt
debug = 1
path_logout = .*/logout.*rr}r(hUhjubaubhW)r}r(hX:Which contains a specification ("use") of which function in which module
should be used to initialize the part. After that comes the name of the
file ("saml_conf") that contains the PySaml2 configuration. The third line
("rememberer_name") points at the plugin that should be used to
remember the user information.rhjáhh h'h[h)}r(h-]h.]h,]h+]h/]uh2Kh3hh4]rhDX:Which contains a specification ("use") of which function in which module
should be used to initialize the part. After that comes the name of the
file ("saml_conf") that contains the PySaml2 configuration. The third line
("rememberer_name") points at the plugin that should be used to
remember the user information.rr}r (hjhjubaubhW)r!}r"(hX<After this, the plugin is referenced in a couple of places::r#hjáhh h'h[h)}r$(h-]h.]h,]h+]h/]uh2K h3hh4]r%hDX;After this, the plugin is referenced in a couple of places:r&r'}r((hX;After this, the plugin is referenced in a couple of places:hj!ubaubjD)r)}r*(hX¢[identifiers]
plugins =
      saml2auth
      auth_tkt

[authenticators]
plugins = saml2auth

[challengers]
plugins = saml2auth

[mdproviders]
plugins = saml2authhjáhh h'jGh)}r+(jIjJh+]h,]h-]h.]h/]uh2K¢h3hh4]r,hDX¢[identifiers]
plugins =
      saml2auth
      auth_tkt

[authenticators]
plugins = saml2auth

[challengers]
plugins = saml2auth

[mdproviders]
plugins = saml2authr-r.}r/(hUhj)ubaubhW)r0}r1(hX2Which means that the plugin is used in all phases.r2hjáhh h'h[h)}r3(h-]h.]h,]h+]h/]uh2K°h3hh4]r4hDX2Which means that the plugin is used in all phases.r5r6}r7(hj2hj0ubaubeubheubhh h'h5h)}r8(h-]r9høah.]h,]h+]r:Uid1r;ah/]uh2K³h3hh4]r<(h=)r=}r>(hXThe applicationr?hhhh h'hAh)}r@(h-]h.]h,]h+]h/]uh2K³h3hh4]rAhDXThe applicationrBrC}rD(hj?hj=ubaubhW)rE}rF(hX"Is as said before extremly simple. The only thing that is connected to
the PySaml2 configuration are at the bottom, namely where the server are.
You have to ascertain that this coincides with what is specified in the
PySaml2 configuration. Apart from that there really are no thing in
application.py that demands that you use PySaml2 as middleware. If you
switched to using the LDAP or CAS plugins nothing would change in the
application. In the application configuration yes! But not in the application.
And that is really how it should be done.rGhhhh h'h[h)}rH(h-]h.]h,]h+]h/]uh2Kµh3hh4]rIhDX"Is as said before extremly simple. The only thing that is connected to
the PySaml2 configuration are at the bottom, namely where the server are.
You have to ascertain that this coincides with what is specified in the
PySaml2 configuration. Apart from that there really are no thing in
application.py that demands that you use PySaml2 as middleware. If you
switched to using the LDAP or CAS plugins nothing would change in the
application. In the application configuration yes! But not in the application.
And that is really how it should be done.rJrK}rL(hjGhjEubaubhW)rM}rN(hXöThere is one assumption and that is that the middleware plugin that gathers
information about the user places the extra information in as value on the
"user" property in the dictionary found under the key "repoze.who.identity"
in the environment.rOhhhh h'h[h)}rP(h-]h.]h,]h+]h/]uh2K¾h3hh4]rQhDXöThere is one assumption and that is that the middleware plugin that gathers
information about the user places the extra information in as value on the
"user" property in the dictionary found under the key "repoze.who.identity"
in the environment.rRrS}rT(hjOhjMubaubeubhh h'Usystem_messagerUh)}rV(h-]UlevelKh+]h,]rWj;aUsourceh h.]h/]UlineK³UtypeUINFOrXuh2K³h3hh4]rYhW)rZ}r[(hUh)}r\(h-]h.]h,]h+]h/]uhhh4]r]hDX2Duplicate implicit target name: "the application".r^r_}r`(hUhjZubah'h[ubaubaUcurrent_sourceraNU
decorationrbNUautofootnote_startrcKUnameidsrd}re(hhLhh}hh8h	jåh
jhh1hNh
juh4]rf(h%hehUUtransformerrgNU
footnote_refsrh}riUrefnamesrj}rkUsymbol_footnotesrl]rmUautofootnote_refsrn]roUsymbol_footnote_refsrp]rqU	citationsrr]rsh3hUcurrent_linertNUtransform_messagesru]rv(h)rw}rx(hUh)}ry(h-]UlevelKh+]h,]Usourceh h.]h/]UlineKUtypejXuh4]rzhW)r{}r|(hUh)}r}(h-]h.]h,]h+]h/]uhjwh4]r~hDX0Hyperlink target "example-sp" is not referenced.rr}r(hUhj{ubah'h[ubah'jUubh)r}r(hUh)}r(h-]UlevelKh+]h,]Usourceh h.]h/]UlineKUtypejXuh4]rhW)r}r(hUh)}r(h-]h.]h,]h+]h/]uhjh4]rhDXAHyperlink target "middleware responsibilities" is not referenced.rr}r(hUhjubah'h[ubah'jUubeUreporterrNUid_startrKU
autofootnotesr]rU
citation_refsr}rUindirect_targetsr]rUsettingsr(cdocutils.frontend
Values
ror}r(Ufootnote_backlinksrKUrecord_dependenciesrNUrfc_base_urlrUhttp://tools.ietf.org/html/rU	tracebackrKUpep_referencesrNUstrip_commentsrNU
toc_backlinksr Uentryr¡U
language_coder¢Uenr£U	datestampr¤NUreport_levelr¥KU_destinationr¦NU
halt_levelr§KU
strip_classesr¨NhANUerror_encoding_error_handlerr©UbackslashreplacerªUdebugr«NUembed_stylesheetr¬Uoutput_encoding_error_handlerrUstrictr®U
sectnum_xformr¯KUdump_transformsr°NU
docinfo_xformr±KUwarning_streamr²NUpep_file_url_templater³Upep-%04dr´Uexit_status_levelrµKUconfigr¶NUstrict_visitorr·NUcloak_email_addressesr¸Utrim_footnote_reference_spacer¹UenvrºNUdump_pseudo_xmlr»NUexpose_internalsr¼NUsectsubtitle_xformr½Usource_linkr¾NUrfc_referencesr¿NUoutput_encodingrÀUutf-8rÁU
source_urlrÂNUinput_encodingrÃU	utf-8-sigrÄU_disable_configrÅNU	id_prefixrÆUU	tab_widthrÇKUerror_encodingrÈUUTF-8rÉU_sourcerÊU</home/lgs/proyectos/yaco/pysaml2/pysaml2/doc/examples/sp.rstrËU	generatorrÌNUdump_internalsrÍNUpep_base_urlrÎUhttp://www.python.org/dev/peps/rÏUinput_encoding_error_handlerrÐj®Uauto_id_prefixrÑUidrÒUdoctitle_xformrÓUstrip_elements_with_classesrÔNU
_config_filesrÕ]Ufile_insertion_enabledrÖKUraw_enabledr×KU
dump_settingsrØNubUsymbol_footnote_startrÙKUidsrÚ}rÛ(jjh}hyhúhôjjh1hh8hhLhHjåjáj;huUsubstitution_namesrÜ}rÝh'h3h)}rÞ(h-]h+]h,]Usourceh h.]h/]uU	footnotesrß]ràUrefidsrá}râh1]rãh%asub.
360core / pysaml2 python

Products

About

Resources

Contact Gemfury
