Forum Discussion
Missing Certificate after redirect
abc.com has no function. It is a legacy URL.
Client doesn't return back to abc.com, everything is handled in APIM.
Certificate is used for authentication. I am not too familiar with F5, so any light you can shed on the redirect would be helpful. Or any information on how to achieve authentication in this case.
rts If abc.com is legacy then you want to change your redirect to a 301 rather than a 307. Now in regards to client authentication, they would need a client certificate for both abc.com and apim-xyz.com in order for things to work after the redirect. Most likely the client certificate is for domain abc.com and since the destination is no longer abc.com they would need the one cert to cover both FQDNs or have two certs with each one having the name for the appropriate destination.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com