servala/servala-portal

Fork 0

Login and registration with VSHN Account #5

New issue

Closed

opened 2025-03-04 09:21:58 +00:00 by tobru · 3 comments

tobru commented

2025-03-04 09:21:58 +00:00

Owner

Stories

As a user, I want to log in using my VSHN Account via OpenID Connect so that I can access the portal securely

As a user, I want to be automatically registered in the portal when I first log in with my VSHN Account so that I can start using the portal immediately

Implementation Notes

The VSHN Account is a Keycloak instance
The OpenID parameters need to be configurable so that they can differ depending on the application's environment

## Stories _As a user, I want to log in using my VSHN Account via OpenID Connect so that I can access the portal securely_ _As a user, I want to be automatically registered in the portal when I first log in with my VSHN Account so that I can start using the portal immediately_ ## Implementation Notes * The VSHN Account is a Keycloak instance * The OpenID parameters need to be configurable so that they can differ depending on the application's environment

tobru added this to the Development Planning project

2025-03-04 09:21:58 +00:00

tobru added the

enhancement

label

2025-03-04 09:22:38 +00:00

tobru added this to the Servala Portal MVP milestone

2025-03-04 09:22:40 +00:00

tobru changed title from ~~Login with VSHN Account~~ to Login and registration with VSHN Account

2025-03-04 09:23:25 +00:00

rixx was assigned by tobru

2025-03-04 09:24:54 +00:00

tobru commented

2025-03-04 13:35:34 +00:00

Author

Owner

@tobru TODO: Figure out how to work in local dev env. Do we need a local Keycloak? Can we use the VSHN Test Keycloak?

rixx referenced this issue

2025-03-09 14:27:46 +00:00

Initialize Django project #8

tobru referenced this issue

2025-03-11 09:05:59 +00:00

High-Level Roadmap #9

tobru commented

2025-03-13 10:57:07 +00:00

Author

Owner

Wo do work with the VSHN Test Keycloak for now, this is the intended allauth configuration:

SOCIALACCOUNT_AUTO_SIGNUP = True
SOCIALACCOUNT_ONLY = True
SOCIALACCOUNT_PROVIDERS = {
    "openid_connect": {
        "APPS": [
            {
                "provider_id": "keycloak",
                "name": "VSHN Account",
                "client_id": "HIDDEN",
                "secret": "HIDDEN",
                "settings": {
                    "server_url": "HIDDEN",
                },
            }
        ]
    }
}

For SOCIALACCOUNT_ONLY we probably still need to be able to log in to Django admin with a local account for now.

And for making the allauth themes look good, we could use https://github.com/harrelchris/django-allauth-themes (maybe just vendor the templates to not rely on the dependency)

Related docs:

https://docs.allauth.org/en/latest/socialaccount/introduction.html

Wo do work with the VSHN Test Keycloak for now, this is the intended allauth configuration: ``` SOCIALACCOUNT_AUTO_SIGNUP = True SOCIALACCOUNT_ONLY = True SOCIALACCOUNT_PROVIDERS = { "openid_connect": { "APPS": [ { "provider_id": "keycloak", "name": "VSHN Account", "client_id": "HIDDEN", "secret": "HIDDEN", "settings": { "server_url": "HIDDEN", }, } ] } } ``` For `SOCIALACCOUNT_ONLY` we probably still need to be able to log in to Django admin with a local account for now. And for making the allauth themes look good, we could use https://github.com/harrelchris/django-allauth-themes (maybe just vendor the templates to not rely on the dependency) Related docs: * https://docs.allauth.org/en/latest/socialaccount/introduction.html

rixx referenced this issue

2025-03-17 08:48:52 +00:00

Login and registration #10

tobru commented

2025-03-17 13:33:42 +00:00

Author

Owner

As discussed, we set SOCIALACCOUNT_ONLY = False for now as the Django admin also uses allauth.

As discussed, we set `SOCIALACCOUNT_ONLY = False` for now as the Django admin also uses allauth.

rixx closed this issue

2025-03-20 09:24:30 +00:00