[keycloak-user] Docker and Invalid token issuer
Lorenzo Luconi Trombacchi
lorenzo.luconi at iit.cnr.it
Tue Feb 19 04:52:44 EST 2019
I think is a hostname problem not a IP problem. The IP can be private but you should reference your keycloak server using always the same hostname, when you get and when you check the token (your applications do the check).
I had a similar problem inside a docker swarm cluster because some applications referenced the keycloak server with an internal name and other with a different or external name.
I hope this helps.
> Il giorno 14 feb 2019, alle ore 20:03, Svyatoslav Babych <s.babych at dataclaritycorp.com> ha scritto:
> Good morning everyone,
> Could you please help me with this, I believe, common problem:
> I setup keycloak in Docker container, and have second container what communicate with Keycloak through private IP.
> I acquire access token through public IP and then send request to this second container. As a result - "Invalid token issuer" exception.
> Unfortunately second container cannot use public IP.
> Appreciate any help with this ?
> Thank you,
> Best regards,
> Svyatoslav Babych | Senior Solution Architect, Technical team Lead
> s.babych at dataclaritycorp.com
> DataClarity Corporation | www.dataclaritycorp.com
> Facebook | Twitter | LinkedIn
> Confidentiality Notice: The information in this email and any attachments is confidential or proprietary and should be treated and marked as “Confidential” DataClarity communication. If you are not the intended recipient of this email, any review, disclosure, copying, or distribution of it including any attachments is strictly prohibited and may be unlawful. If you have received this email in error, please notify the sender and immediately and permanently delete it and destroy any copies. Any information contained in this email is subject to the terms and conditions expressed in any applicable agreement.
> keycloak-user mailing list
> keycloak-user at lists.jboss.org
More information about the keycloak-user