Moving V2.1 SP from test server to production server

[hanaa]

Cantor, Scott E. wrote
> 
> On 6/29/12 1:26 PM, "hanaa" <hanan.ebraheem@> wrote:
>>
>>I have Shibboleth SP 2.x working properly on Production Server, but we
>>plan
>>to do some updates and need to test shibboleth on test Server first before
>>apply the change to Production. in this case do I need to register for
>>another Metadata? beside changing the Host name to the test Server and
>>coying over attribute-map and attribute policy over to test server?
> 
> Yes, no, maybe. There's no single answer to any of that. You have to
> change what you have to change based on what's being exposed as different.
> 
> If you change a client's /etc/hosts file you can make any server look like
> any server name you want, so you don't necessarily have to change
> anything. It all depends.
> 
> If you want better answers, ask better questions. Be specific. What are
> your assumptions, what are your peering models with IdPs, who's consuming
> what metadata and where is the metadata managed? Etc.
> 
> 
> 
> 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"/> 
> 
> 
> --
> To unsubscribe from this list send an email to users-unsubscribe@
> 


--
View this message in context: http://shibboleth.1660669.n2.nabble.com/Moving-V2-1-SP-from-test-server-to-production-server-tp3810847p7580342.html
Sent from the Shibboleth - Users mailing list archive at Nabble.com.