Microcks Ui doesnt show APIs & Services

[jennerEVRFLL]

Hello,

It seems I have a problem with my k8s v1.20.11 installation of microcks. I´ve deployed microcks on two company clusters and local minikube instance. I have tested it with different versions locally and in the cluster. The minikube instance works fine but the cluster installations have a strange behaviour.

I can create APIs:

But only get a blank page when try to list them.

The pods do not return any error messages except this warning:

Podlog

08:51:54.822 [DEBUG] io.github.microcks.web.InvocationController - Getting invocations stats for last 20 days
08:51:54.822 [DEBUG] io.github.microcks.web.InvocationController - Getting top 20 invocations stats for day 20211215
08:51:54.822 [WARN] org.keycloak.adapters.RequestAuthenticator - SSL is required to authenticate. Remote address 100.x.x.34 is secure: false, SSL required for: EXTERNAL .

The network analysis of Chrome and Firefox shows the following errors:

[lbroudoux]

Thanks a lot for reporting this issue!

Are you using provided Keycloak or external one? In case of external one, are you using https endpoint?

[jennerEVRFLL]

Hi @lbroudoux

thanks for the reply. Yes we use a external Keycloak (Keycloak Operator) and a https endpoint because we also use a apicurio instance.

Here are some information about the configuration.

Helm Values

keycloak:
  install: false
  realm: apicurio
  url: apicurio.xxx.xxx.one 
  privateUrl: https://apicurio.xxx.xxx.one/auth

Configured Keycloak Clients:

Mocking feature works but also displays a blank page on mickrocks:

[lbroudoux]

The #526 seems to face the same odd empty page. Maybe related?
I'm currently building a new cluster to test this out. Stay tuned

[lbroudoux]

Looking at your settings, it seems that both keycloak.url and keycloak.privateUrl are pointing to the same URL. You wouldn't need keycloak.privateUrl though.

[lbroudoux]

That said, I've tried with this setting - pointing on an external Keycloak using the same secured Ingress for both url and privateUrl and did not succeed reproducing it (yet!).

[lbroudoux]

Hey @jennerEVRFLL

Any news on this one ?

[jennerEVRFLL]

Hi @lbroudoux not yet. But we setting up a new Cluster right now. I'll keep you updated.

[frdrcrlt]

Hi @lbroudoux, I have the same empty page when I import an API specification (OCP 4.8.27, Microcks Operator 1.5.0)

Here is the log in the my-microcks Pod application :

16:01:48.879 [WARN] org.keycloak.adapters.RequestAuthenticator - SSL is required to authenticate. Remote address xxx.xx.xx.x is secure: false, SSL required for: EXTERNAL .

[carolgschwend]

Hi @lbroudoux, We are experiencing the same problem and getting the same error when deployed with existing keycloak instance.

We deployed image and chart 1.2.1. Below image shows local deployment with internal keycloak on the left vs an environment cluster with external keycloak on the right.

[carolgschwend]

I found a workaround. I entered part of my spec title in the 'Filter by Name...' field on the APIs & Services page and it found and listed my spec!

The hasRepositoryFilterFeatureEnabled check in ServicesPageComponent seems to prevent the service lookup unless something is entered in the filter.

Logs are still full of these errors:
[WARN] org.keycloak.adapters.RequestAuthenticator - SSL is required to authenticate. Remote address xxx.xx.xx.x is secure: false, SSL required for: EXTERNAL .

[lbroudoux]

Hey @carolgschwend

The hasRepositoryFilterFeatureEnabled check in ServicesPageComponent seems to prevent the service lookup unless something is entered in the filter.

This is a weird behavior as the hasRepositoryFilterFeatureEnabled should just condition the fetching of available services labels for filtering... Default is to fetch all services (see default) and entering a new name just call the /api/service/search endpoint that is also secured using Keycloak...

[WARN] org.keycloak.adapters.RequestAuthenticator - SSL is required to authenticate. Remote address xxx.xx.xx.x is secure: false, SSL required for: EXTERNAL .

I assume you've got this message on the cluster that is using external Keycloak. Please make sure this endpoints is actually secured. Microcks assumed it is (just prepending https:// to the keycloak.url param of your chart if you're not using a privateUrl) but I think the keycloak connector do extra checks that lead to above messages and bad behavior of the connector.