Skip to main content
Solved

impossible to connect to CLAPI when password contains a '&' character

  • September 26, 2022
  • 8 replies
  • 133 views

Forum|alt.badge.img+4

Hello,

I successfully connect to UI, but impossible to connect to CLAPI when user password contains a '&' character.

When I change the password for a simple one, both UI and CLAPI authentications are OK.

Latest Centreon.

Best answer by sims24

I can see that it will be fixed in the upcoming 22.10.0 and the 22.04.6 (which is already out from what I know). 

 

Best,

8 replies

sims24
Forum|alt.badge.img+19
  • Ranger ***
  • 330 replies
  • September 26, 2022

Are you enclosing password with quotes? 


Forum|alt.badge.img+4
  • Author
  • Steward **
  • 8 replies
  • September 26, 2022

Are you enclosing password with quotes? 

yes


sims24
Forum|alt.badge.img+19
  • Ranger ***
  • 330 replies
  • September 26, 2022

This is a bug, I reproduced it.


Forum|alt.badge.img+4
  • Author
  • Steward **
  • 8 replies
  • October 18, 2022

WIll this bug be solved in the next release?


sims24
Forum|alt.badge.img+19
  • Ranger ***
  • 330 replies
  • Answer
  • October 19, 2022

I can see that it will be fixed in the upcoming 22.10.0 and the 22.04.6 (which is already out from what I know). 

 

Best,


Forum|alt.badge.img+4
  • Author
  • Steward **
  • 8 replies
  • October 20, 2022

Generally speaking where can I follow this kind of issue… I didn't find it on GitHub issue.


sims24
Forum|alt.badge.img+19
  • Ranger ***
  • 330 replies
  • October 20, 2022

You have to check the release notes, cause we don’t create a Github issue for each bug we spot through the watch … 


  • 266 replies
  • October 17, 2024

You have to check the release notes, cause we don’t create a Github issue for each bug we spot through the watch … 

Which is sad imho.

Open source software has never implied an open development strictly speaking, But an open development is a reality for a majority of open source projects though, and, if I’m not mistaken, was the case for Centreon since the beginning and through a couple of years ago.

What was the issue for Centreon to rely only on a publicly available bug tracker instead of having a private corporate one internally as the main tracker? Obviously, even issues reported in Github leads to internal tickets, processed internally, and then only the final status is reported back to Github to close the ticket there.

I can understand this in some very peculiar occasions regarding security (if at all…), but I’m pretty sure this don’t encourage community contributions.