Allow unauthenticated connections to /cluster/1.0#112
Conversation
masnax
requested review from
markylaing,
roosterfish and
tomponline
as code owners
masnax
changed the title
…r/1.0 Untrusted systems should still be able to view this non-sensitive information. Signed-off-by: Max Asnaashari <max.asnaashari@canonical.com>
|
@masnax why do we need this? |
This doesn't explain what this PR fixes? |
This is just server information about the cluster. Like LXD's It was restricted to cluster members but all of this information is already available to all cluster members locally. Nothing here is that sensitive so I thought it would be more flexible to allow untrusted systems to check it, so they can see if the cluster is functional or not. In LXD sensitive information is appended to the returned data only when the connection is from a trusted source, so I thought we could do something similar if we ever do want to add sensitive information here. |
3 participants
Untrusted systems should still be able to view this non-sensitive information. (name, address, database status, and soon likely API extensions).