Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Do not require the CAS service URL setting (use public_baseurl instead). (#9199) | Patrick Cloke | 2021-01-26 | 1 | -5/+7 |
| | | | | The current configuration is handled for backwards compatibility, but is considered deprecated. | ||||
* | Land support for multiple OIDC providers (#9110) | Richard van der Hoff | 2021-01-15 | 1 | -1/+1 |
| | | | | | | | | | | | | | | | | | | | | | | | This is the final step for supporting multiple OIDC providers concurrently. First of all, we reorganise the config so that you can specify a list of OIDC providers, instead of a single one. Before: oidc_config: enabled: true issuer: "https://oidc_provider" # etc After: oidc_providers: - idp_id: prov1 issuer: "https://oidc_provider" - idp_id: prov2 issuer: "https://another_oidc_provider" The old format is still grandfathered in. With that done, it's then simply a matter of having OidcHandler instantiate a new OidcProvider for each configured provider. | ||||
* | Improve the sample config for SSO (OIDC, SAML, and CAS). (#8635) | Patrick Cloke | 2020-10-30 | 1 | -12/+34 |
| | |||||
* | cas: support setting display name (#6114) | Valérian Rousset | 2019-10-11 | 1 | -0/+3 |
| | | | Now, the CAS server can return an attribute stating what's the desired displayname, instead of using the username directly. | ||||
* | Refactor HomeserverConfig so it can be typechecked (#6137) | Amber Brown | 2019-10-10 | 1 | -0/+2 |
| | |||||
* | Don't load the generated config as the default. | Richard van der Hoff | 2019-06-24 | 1 | -1/+1 |
| | | | | It's too confusing. | ||||
* | Pass config_dir_path and data_dir_path into Config.read_config. (#5522) | Richard van der Hoff | 2019-06-24 | 1 | -1/+1 |
| | | | | | | * Pull config_dir_path and data_dir_path calculation out of read_config_files * Pass config_dir_path and data_dir_path into read_config | ||||
* | Attempt to make default config more consistent | Richard van der Hoff | 2019-02-19 | 1 | -0/+1 |
| | | | | | | The general idea here is that config examples should just have a hash and no extraneous whitespace, both to make it easier for people who don't understand yaml, and to make the examples stand out from the comments. | ||||
* | fix typo | Matthew Hodgson | 2017-10-29 | 1 | -1/+1 |
| | |||||
* | copyrights | Matthew Hodgson | 2016-01-07 | 1 | -1/+1 |
| | |||||
* | Allow hs to do CAS login completely and issue the client with a login token ↵ | Steven Hammerton | 2015-11-05 | 1 | -1/+1 |
| | | | | that can be redeemed for the usual successful login response | ||||
* | Add service URL to CAS config | Steven Hammerton | 2015-11-04 | 1 | -0/+3 |
| | |||||
* | Add config option to disable password login | Erik Johnston | 2015-10-22 | 1 | -1/+2 |
| | |||||
* | Default cas_required_attributes to empty dictionary | Steven Hammerton | 2015-10-12 | 1 | -1/+1 |
| | |||||
* | Support multiple required attributes in CAS response, and in a nicer config ↵ | Steven Hammerton | 2015-10-12 | 1 | -15/+4 |
| | | | | format too | ||||
* | Allow optional config params for a required attribute and it's value, if ↵ | Steven Hammerton | 2015-10-12 | 1 | -0/+15 |
| | | | | specified any CAS user must have the given attribute and the value must equal | ||||
* | Provide ability to login using CAS | Steven Hammerton | 2015-10-10 | 1 | -0/+39 |