Hi Docente!
Answering your specific questions:
1. Organization info is, basically, the setting that govern how other parties will see your instance. Technically, the values here are included in your instance metadata Organization description, how other parties use it is up to them. The values you put there is irrelevant for authentication process (as far as I can tell), but you should provide them for other parties that actually use them for something.
2. This puzzled me for some time as well. Actually, the configuration model is built in a way that there's only one active configuration at a time, but entire history of changes is retained + rollbacks are allowed. If you need to change something - just add new one - it will automatically pick values of last active configuration and replace it when saved, essentially "updating" effective configuration.
3. Not sure what are you asking here. If we're still talking about SAML Configuration, Entity Id is an arbitrary string that uniquely identifies your instance. It might be anything you want, but a best practice is to put your instance URL there, to ensure it's unique. SAML Identity Providers identify requests by this entity ids, so you want it to be unique, but not secret. I'm not an expert, but with my current understanding if there're two instances with same entity id registered with the same Identity Provider, one (maybe random one) of the instances will get incorrect SAML assertions and fail authentication - so it's not a security risk.
4. Not explicitly asked, but mentioned: you add IdP metadata in admin/third_party_auth/samlproviderconfig/, not admin/third_party_auth/samlconfiguration. SAML Configuration is for configuring your instance. SAML Provider Configuration is for configuring IdPs you want to use (one per IdP).
Regards,
Eugeny
понедельник, 21 сентября 2015 г., 17:43:59 UTC+3 пользователь Docente Edoc написал: