idp 4.3.1 - status after disabling modules

[Felix Gorschlüter]

Hello together,

if I want to deactivate a modules in Shibboleth IDP (4.3.1) I achieve it 
by (e.g. idp.oidc.common):
```
/opt/shibboleth-idp/bin/module.sh --disable idp.oidc.common.3
...
Disabling idp.oidc.common.3...
[OK]
```

I interpret "[OK]" as: module disabled successfully. But:

```
/opt/shibboleth-idp/bin/module.sh -l
...
Module: idp.oidc.common.3 [ENABLED]
...
```

for "idp.oidc.OP.2" I get "[DISBALED]" as expected.

Maybe some modules cannot be disabled. In any way I find it unhandy to 
receive "OK". I'd like to understand this behaviour because I have an 
Ansible task to manage plugins and modules. I'd like to be able to 
enable / disable e.g. OIDC. Currently I implemented it cleanly so the 
playbook exits with error if it recognises: after disabling X, X is not 
disabled.

How do I handle this? Do I try to disable X in every run of the playbook 
and ignore the outcome? Should I stop disabling modules at all after I 
installed them once?

Best regards and thank you for answering all these questions from all 
over the world day in, day out
Felix


-- 
Dr. rer. nat. Felix Gorschlüter
Wissenschaftlicher Mitarbeiter (Identitätsmanagement)

Zentrum für Informations- und Medientechnologie
Gebäude 25.41, Raum 01.31

Heinrich-Heine-Universität Düsseldorf
Universitätsstraße 1
40225 Düsseldorf

Postanschrift: 40204 Düsseldorf

Telefon: +49 211 81 15041
E-Mail: felix.gorschlueter at hhu.de

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4852 bytes
Desc: Kryptografische S/MIME-Signatur
URL: <http://shibboleth.net/pipermail/users/attachments/20240513/9a479fa2/attachment.p7s>