Hm, can someone maybe provide a little bit more explanation, about changes in the intented use (if any), and the available settings that remain with the new YNH 12 portal implementation? (Iām sorry, I also could not yet fully āgraspā or āgrokā this part from the announcement.)
Here is another related use-case with (to me) unknown support state that worked really nice with YNH 11:
- Main domain set to a possibly hard-to-remember, maybe even impossible to change, reverse-DNS Domain. (Used as smtp mail-out domain by all configured domains)
- While allowing users to log in on a subdomain of their āusualā domain. (Itās much simpler to explain own users to just use e.g. to
https://apps.example.orgif they want or need to sign in to something. Whileexample.organdwww.example.orgcan just redirect/host some (public) app or website.
In YNH 11 the domain allowing the login could be configured by having a file /etc/ssowat/conf.json.persistent with:
{ "portal_domain": "apps.example.org" }
Result: Except for the button āuser interfaceā (only present?) in the adminās web interface, everything seems to point to the correct portal domain, and work perfectly.
-
Is this expected to break when upgrading to YNH 12?
-
Do you see an alternative solution that does not require the users to use long yunohost login url/sub-paths?
PS: As reference, that āportal_domainā configuration option had come up e.g. in this thread: