Moving V2.1 SP from test server to production server
hanaa
hanan.ebraheem at gmail.com
Fri Jun 29 22:15:05 BST 2012
Thanks Scott,
our Metadata managed by UKfederation. Shibboleth Configuration
(shibboleth2.xml) is the same for all our production servers (same host name
and port number). currently I configured Test Server with different host
name, but same port as production in apache.httpd and shibboleth2.xml. first
I am able to let user select its home organization, but after user
authenticated, it does not return to my Application as in production, it
returns to apache index.html file.
- while tracing redirect requests I could see Idp post Response to the
production not to test. I am not sure if this is metadata Issue as in
Metadata configuration it sepcifies "AssertionConsumreService" location
which is different should be different than production
for example
<md:AssertionConsumerService
Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
Location="https://hostname/Shibboleth.sso/SAML2/POST" index="1"/>
but for Test Server it should AssertionConsumerService should be located at
different location since Host Name is different, something like
<md:AssertionConsumerService
Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
Location="https://test_host_name/Shibboleth.sso/SAML2/POST" index="1"/>
--
View this message in context: http://shibboleth.1660669.n2.nabble.com/Moving-V2-1-SP-from-test-server-to-production-server-tp3810847p7580340.html
Sent from the Shibboleth - Users mailing list archive at Nabble.com.
More information about the users
mailing list