Store authentication methods in database

[ksl28]

Summary of the new feature / enhancement

We have several installations where we have a Prod / Dev instances, that are seperated by using different databases and different Git branches (same repo).

Since OpenID settings are stored in the authentication.ps1 file, this file is also synced from Dev to Prod branch - meaning we have to use the same App registration in Entra ID, with multiple return URLs.

New security requirements mean, that we would like to avoid having the same app registration, for multiple environments.

Proposed technical implementation details (optional)

Allow an option to store the OpenID settings in the database, so that it CAN be unique per environment

[adamdriscoll]

You can do this now:

https://docs.powershelluniversal.com/config/repository#database-resources

{
    "Data": {
        "Persistence" : {
            "AuthenticationMethod": "Database",
        }
    }
}

[ksl28]

You can do this now:

https://docs.powershelluniversal.com/config/repository#database-resources

{
    "Data": {
        "Persistence" : {
            "AuthenticationMethod": "Database",
        }
    }
}

That one feature i wasnt aware of - that is actually nice!

We still want to have the rest of our "system files" in the .ps1 files - but the authentication one, have that in the database.
Hope that makes sense 👍

[RockoTheeHut]

@adamdriscoll is there a list of specific class type names that can be used?