Hi all,
Apologies for the previous message, I mis-clicked the "send" button before
finishing completely - here's my point #2 in its entirety:
2) This one will need a little context, so I better explain our
architecture:
We don't have a single central weblogin server, instead we have one
machine (login.uniba.sk) running the web-front, while another
(cosign.uniba.sk) runs the cosign daemons. Hence, our Apache module
cosign.conf on a protected service looks like this:
...
CosignHostname cosign.uniba.sk
CosignRedirect https://login.uniba.sk/
...
Looking at Cosign_Schema.xml, I got the impression that the IIS7 module
might not support this. More specifically the following section seems to
indicate that the web-front and the daemon need to be on the same
server:
<element name="webloginServer">
<attribute name="name" type="string"/>
<attribute name="loginUrl" type="string"/>
<attribute name="port" type="int" defaultValue="6663"/>
<attribute name="postErrorRedirectUrl" type="string"/>
</element>
Am I correct in assuming that the module will redirect a user's browser
to <loginUrl> and attempt to validate a user's session by consulting the
daemon it expects to find at <name>:<port>? Will it behave as expected
with the following settings?
<Cosign>
<webloginServer name="cosign.uniba.sk"
loginUrl="https://login.uniba.sk/?"; port="6663"
postErrorRedirectUrl="https://login.uniba.sk/post_error.html"; />
...
</Cosign>
?
Thanks in advance!
Mgr. Peter Kopáč
CIT UK
e-mail: [email protected]
tel: 02/592 44 965 voip: 11965
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Cosign-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cosign-discuss
