03-13-2015 04:09 AM - edited 03-10-2019 10:32 PM
Hi There, I am struggling to find any information about Guest Credential Propagation in 1.3
I have 1 x Admin 1 x Backup admin Node 3 x PSN's
In 1.2 Each PSN hosted a guest portal/guest admin portal. As far as I can see that's now changed with 1.3 with 1 URL pointing to one PSN. We have multiple PSN's in different geographical zones to keep the authentication latency down but I am not sure how long it takes for the PSN where the single URL points to update all the PSN's in the deployment.
Does any one have any insight/ done this?
03-14-2015 03:42 PM
Not sure where you are seeing this ? All PSNs still have the guest portal.
03-16-2015 02:13 AM
Hi Jan, its more the sponsor portal that is the issue as there is only one URL into that portal. So that portal is on just one PSN/url as far as I am aware. Happy to be told otherwise!
03-16-2015 12:32 PM
Well, that is only because you are putting a fqdn in there, you don't actually have to. However if you wan't redundancy, you should probably use a load-balancer for that specific url/ip
03-16-2015 01:07 PM
If you remove that fqdn, and then try the Portal Test URL link up to the rigth of the name of the portal, you will see the actual url, this should be possible to use on any PSN
https://<any psn>:8443/sponsorportal/PortalSetup.action?portal=<sponsor portal id number>
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide