Hello,

Thanks for the tutorial

question: where should we configure url redirect on centreon 22.04.7 please

because on the AZURE side, I have configured the same url that you shared

and I have the following error

• To configure your Authentication you will need to provide a redirect uri.???

The format should be <scheme>://<your_domain_name>/centreon/authentication/providers/configurations/openid

Thanks in advance

Hello, you have to go to Authentication Menu > Add a Platform > Then on the rightside panel you can click on Web, then here you will be able to configure your url redirect. 

According to your message your redirect uri is correctly formated on centreon side but doesn’t match the url redirect in your Azure AD application

Hello,

Thanks for your tutorial.

I followed all the steps, but I have an error after AzureAD login. It seems that token url is unreacheable (It isn’t when I type it in my browser)

Do you have any idea of where the issue may come from ?

kind regards

Hello @samaga777 

you have to try this url in Identity provider

https://login.microsoftonline.com/*****************************/oauth2/v2.0

Hello, I found a way to make it work.

What I didn’t mention is that this server works behind a corporate proxy. The connection towards the “/token” endpoint is made by the webserver (I always thought that this connection was made by the end-user ).

Problem is that even by adding proxy in “ui settings” or as an evironment variable ($http_proxy), proxy is ignored.

So I manually added the proxy as a CURL options directly in this file:

/usr/share/centreon/src/Core/Security/Authentication/Domain/Provider/OpenIdProvider.php

Now the token url is available and the oidc connection can happen 

If someone knows a “proper” method, I’m happy to learn

im getting the following error when trying to login, any assistance is appreciated!
 

@simonclarke2000  is your introspection token field empty ?

For me it only worked with userinfo url and leaving the introspect empty

thank you so much @samaga777, that has worked for me! 

@idinar I already tried that but I didn’t work for me, that’s why I had to change the code..

Ok, I found a better solution myself. 

I put the environment variables at apache level. Now it works without modifying centreon code.

Hello,

Thanks for your tutorial.

I followed all the steps, but I have an error when i click on connect with openID.

My configuration is :

i’ve create a user like this :

Bonjour,

Le message d’erreur indique qu’il n’y a pas d’adresse de redirection. L’avez-vous configurée dans AzureAD ?

J’ai fourni l’url à l’admin AzureAD. Je penses qu’il l’a ajouté ou il faut.

Y a t-il un flux réseau à ouvrir? 

A quel endroit je peux observer les logs d’erreur (s’il y en a) ?

Le message d’erreur est du côté AzureAD et spécifie bien que l’URL n’est pas indiquée…. donc il faut vérifier que l’admin a bien ajouté l’adresse.

Les logs sont visibles dans l’interface AzureAD, mais je ne sais pas si cette erreur est loguée.

Pas d’ouverture de flux à faire à ma connaissance.

Bonjour @samaga777,

on a débloqué la situation concernant le premier message d’erreur.

Nous rencontrons maintenant ton erreur idle timeout probablement en rapport aussi avec un proxy chez nous. On creuse de ce côté là avec nos tech réseau.

Merci

@samaga777 Hello,

what file should be modified so that when connecting to Azure AD, centreon uses the proxy?

Thank you

Hello @Patrick 

I added the lines in the apache config file.

In my case, here: /etc/httpd/conf.d/10-centreon.conf

Regards,

@samaga777 

Thank you, it’s done now, with add proxy in to the file.

Bonjour,

On a finalement ouvert les flux entre le central et internet pouir être sur qu’aucun équipement réseau ne bloque.

J’atteins bien le système d’authentification microsoft. Login->password->envoi du code de vérif SMS→ puis j’obtiens l’erreur 

Détail des logs /var/log/centreon/centreon-web.log

n2023-05-15T08:34:28+0200] 0DEBUG] :EventSubscriber\UpdateEventSubscriber:69]: Checking if route matches updates endpoint
p2023-05-15T08:34:28+0200] 0INFO] 8Core\Security\Authentication\Domain\Provider\OpenIdProvider:260]: Start authenticating user... {"provider":"openid"}
i2023-05-15T08:34:28+0200] 0INFO] 8Core\Security\Authentication\Domain\Provider\OpenIdProvider:437]: Send request to external provider for connection token...
e2023-05-15T08:34:28+0200] 0ERROR] :Core\Security\Authentication\Domain\Provider\OpenIdProvider:819]: invalid status code return by external provider, y401] returned, d200] expected
2023-05-15T08:34:29+0200] 0DEBUG] :EventSubscriber\UpdateEventSubscriber:69]: Checking if route matches updates endpoint
p2023-05-15T08:34:29+0200] 0DEBUG] :EventSubscriber\UpdateEventSubscriber:69]: Checking if route matches updates endpoint
p2023-05-15T08:34:29+0200] 0INFO] 8Core\Application\Platform\UseCase\FindInstallationStatus\FindInstallationStatus:47]: check installation status of centreon web
o2023-05-15T08:34:29+0200] 0NOTICE] 3Security\Domain\Authentication\AuthenticationService:69]: tAUTHENTICATION SERVICE] token not found
t2023-05-15T08:34:29+0200] 0NOTICE] 3Security\Domain\Authentication\AuthenticationService:69]: tAUTHENTICATION SERVICE] token not found
t2023-05-15T08:34:29+0200] 0DEBUG] :Core\Security\Authentication\Infrastructure\Repository\DbWriteTokenRepository:61]: Deleting expired refresh tokens
2023-05-15T08:34:29+0200] 0DEBUG] :Core\Security\Authentication\Infrastructure\Repository\DbWriteTokenRepository:82]: Deleting expired tokens which are not linked to a refresh token
a2023-05-15T08:34:29+0200] 0DEBUG] :EventSubscriber\UpdateEventSubscriber:69]: Checking if route matches updates endpoint
p2023-05-15T08:34:29+0200] 0DEBUG] :EventSubscriber\UpdateEventSubscriber:69]: Checking if route matches updates endpoint