[BUG]: Driver should not be expecting a secret which is not used at all for PowerMax when authorization is enabled

[shanmydell]

Bug Description

Driver should not be expecting a secret which is not used at all for PowerMax when authorization is enabled

We are requesting the customer to create a secret without a username and password, a stale entry that will not be validated and used by the driver and should be skipped. We should validate if authorization is enabled and make this secret optional

Logs

https://github.com/dell/csi-powermax/blob/main/samples/secret/secret.yaml

apiVersion: v1
kind: Secret
metadata:
name: powermax-creds
namespace: powermax
type: Opaque
data:

set username to the base64 encoded username

if authorization is enabled, username will be ignored

username: bm90X3RoZV91c2VybmFtZQ==

set password to the base64 encoded password

if authorization is enabled, password will be ignored

password: bm90X3RoZV9wYXNzd29yZA==

Uncomment the following key if you wish to use ISCSI CHAP authentication (v1.3.0 onwards)

chapsecret:

Screenshots

No response

Additional Environment Information

No response

Steps to Reproduce

Install the driver without secret when authorization is enabled, it will be crashing

Expected Behavior

Install the driver with this secret being optional/not required when authorization is enabled

CSM Driver(s)

PowerMax

Installation Type

No response

Container Storage Modules Enabled

No response

Container Orchestrator

NA

Operating System

NA

[csmbot]

@shanmydell: Thank you for submitting this issue!

The issue is currently awaiting triage. Please make sure you have given us as much context as possible.

If the maintainers determine this is a relevant issue, they will remove the needs-triage label and respond appropriately.

---

We want your feedback! If you have any questions or suggestions regarding our contributing process/workflow, please reach out to us at [email protected].

[anandrajak1]

/sync

[csmbot]

link: 30420

[thikade]

I agree, we simply put user: "dummy" and password: "dummy" in there, to satisfy the operator.
.... bit weird though, that you can then see user: "dummy" in the controller logs ...