As a SQ Instance Admin i want to see the current email configuration in plaintext somewhere

Hello :wave:

Try to describe the problem or opportunity you are seeing and why it matters. The closer you stick to this topic template, and the more information you provide, the better chance you have to generate a real discussion.

A few questions to help you:

  • What are you trying to accomplish?
    I want to debug or recreate or answer questions relating to the email configuration used

  • Why does this matter to you?
    Because i want to recreate it, debug it or answer questions concerning it

  • How would that look in SonarQube? Alternatives?
    Create API for querying or display email connection details in plaintext in Admin-GUI after manual interaction

  • How would we know it works well?
    The plaintext email connection details are inside the API response or shown in GUI

  • Why should it be a priority now?
    Because everyone who wants to send emails needs this.

Make sure to check out our product roadmap as well, to see if your need is already being considered.

  • nothing there yet

Lets see which interesting followup questions this will trigger…

cheers,
Daniel

Hello Daniel,

Thank you for your insight.

We plan to migrate soon SonarQube email configuration from basic authentication to modern authentication. We will review the display of saved fields by then.

Thanks.

Hello Ilham,

after finding SONAR-22516 i am a little bit scared now. Because i do not know if i am able to use oauth for authenticating with our email setup.

I think it still would be beneficial to be able to use basic auth (only through an encrypted channel like tls/https!) when talking with the email server, but i am no security expert. I currently just only know that way of configuration. And maybe that would hinder me to update to the latest version if it would be taken away.

My - maybe badly phrased - request was, to be able to check the used values that i entered … so that i am able to self-correct any mistakes, which maybe originate from entering the wrong data into the (currently masked) input-fields in the gui.

cheers
Daniel