Open antonioberben opened 2 years ago
Hi, When is this issue planned to be resolved?
@chrisgaun , please, could you help on this? Thank you
@sirrapa I don't have it as a blocker. Can you lmk the priority. I had not prioritized it.
@antonioberben We have attempted to reproduce this issue, but we have not yet succeeded. Do you have more details that we might be able to use (i.e., details about the overall environment, keycloak configuration file, portal controller configuration file)?
Update: Still waiting to hear back from customer on this, unable to reproduce in engineering or field.
From our tests, we were not able to reproduce anymore. However, it could be due to cert format with SAN. We are getting back to the customer to see if that is the reason
Lowering priority and removing from sprint until we hear this is a priority again.
Using version: 1.1.0
Following the documentation: https://docs.solo.io/gloo-portal/main/guides/portal_features/custom_ca/
After creating the certificates and creating a Portal resource (i.e. you can follow the workshop labs -> https://workshops.solo.io/gloo-workshops/gloo-portal) the Portal resource state returns following error:
Our keycloak is secured using a self-signed certificate.
Same happened with private certiifcates.
The full error looks like this:
Thank you.