Expose OIDC config parameters

[arvchristos]

This MR exposes OIDC configuration parameters in the default config entrypoint script and the env variables. Essentially, misp-docker can now easily work with external SSO providers, a requirement for our use-case.

Settings are configured according to https://github.com/MISP/MISP/blob/2.4/app/Plugin/OidcAuth/README.md

By default, OIDC is disabled but can be enabled with the env variable OIDC_ENABLE.

[ostefano]

Thank you @arvchristos , I like this.

We are using OIDC as well, so might take this as an opportunity to merge some additonal logic.
I will iterate later today.

[ostefano]

Note that this is not idempotent (can't recall the exact behavior :S).

Best fix, is to reset the value before setting it.

sudo -u www-data php /var/www/MISP/tests/modify_config.php modify "{
            \"Security\": {
                \"auth\": \"\"
            }
}" > /dev/null 

[arvchristos]

I thought of this but this step is already happening at

misp-docker/core/files/configure_misp.sh

Line 192 in 526c47a

sudo -u www-data php /var/www/MISP/tests/modify_config.php modify "{

which is by default executed and cannot be disabled with a flag.

[ostefano]

I would add some example re the data type

[arvchristos]

Fixed

[ostefano]

Same thing here.

[arvchristos]

Fixed

[ostefano]

Not sure whether we want default values if not working

[ostefano]

Let me rephrase it. I would rather remove default values, and add some checks when setting up oidc (e.g., if not all values are set, error out).

[arvchristos]

Done and added a generic utility which can be used for other configuration functions in the future

[ostefano]

Nice. I see the output is redirected to stderr. Should we leave it like that?

[arvchristos]

Actually no, you are totally right, fixed

[ostefano]

LGTM