The UI defaults topic properties when the user does not have access to describe the topic

[yeikel]

Issue submitter TODO list

• I've looked up my issue in FAQ
• I've searched for an already existing issues here
• I've tried running main-labeled docker image and the issue still persists there
• I'm running a supported version of the application which is listed here

Describe the bug (actual behavior)

When an user does not have access to describe a topic, the /clusters/<cluster>/topics/<topic> endpoint returns only what it knows. For example, cleanUpPolicy:UNKNOWN as expected

For example, see the following response:

{
    "name": "<topic>",
    "internal": false,
    "partitions": [
        {
            "partition": 0,
            "leader": 7,
            "replicas": [
                {
                    "broker": 7,
                    "leader": true,
                    "inSync": true
                },
                {
                    "broker": 2,
                    "leader": false,
                    "inSync": true
                },
                {
                    "broker": 3,
                    "leader": false,
                    "inSync": true
                }
            ],
            "offsetMax": 0,
            "offsetMin": 0
        }
    ],
    "partitionCount": 1,
    "replicationFactor": 3,
    "replicas": 3,
    "inSyncReplicas": 3,
    "bytesInPerSec": null,
    "bytesOutPerSec": null,
    "segmentSize": 0,
    "segmentCount": 0,
    "underReplicatedPartitions": 0,
    "cleanUpPolicy": "UNKNOWN",
    "keySerde": null,
    "valueSerde": null
}

However, the UI seems to be defaulting the values which is not only misleading but also very confusing

Expected behavior

If the user does not have access to describe the topic, the UI should show that or not do any defaulting that may be misleading

Your installation details

21590d8

Steps to reproduce

• Create a user that does not have access to the describe command in a cluster
• Create a topic
• Navigate to the configuration properties of the topic
• Observe how many properties are defaulted despite not having access

Screenshots

No response

Logs

No response

Additional context

No response

[josianeReis]

@yeikel Could you assign this to me, I would like to contribute

[yeikel]

@yeikel Could you assign this to me, I would like to contribute

Hi @josianeReis

Thanks for your interest 🙂

I don't have the ability to assign issues, but you're open to picking it up directly, given that nobody is working on it

@Haarolean May be able to assign it to you, but that's not a requirement to start contributing