Michael Barz
Michael Barz
@AlexAndBear @kobergj I think you already implemented some improvements. Can this be closed?
@TheOneRing Do you have a hunch why this happens? The URL `https://owncloud.mydomain.net/index.php/apps/oauth2/authorize?` is from oc10? @doruchan Is it possible, that this local user has been used against ownCloud10 before?
> Is this a normal response for the page "owncloud.mydomain.net/status.php"? > > ``` > { > "installed": true, > "maintenance": false, > "needsDbUpgrade": false, > "version": "10.11.0.0", > "versionstring": "10.11.0",...
> The client only uses the .well-known from the system entered during setup. So `https://owncloud.mydomain.net/.well-known/openid-configuration` should point to your keycloak server. But how can an oc10 Oauth2 url come from...
@doruchan Has the issue been resolved after recreating the account?
There is a config var in our example deployment to rewrite the well known.
Latest is working fine now. @TheOneRing I also saw that URL `https://owncloud.mydomain.net/index.php/apps/oauth2/authorize?` in another ticket. It was a new central post https://central.owncloud.org/t/ocis-5-x-and-keycloak-25-auto-relogin-fails-after-restart-of-the-desktop-client/49527 How on earth could something like this happen...
The issue seems to be that the .well-known endpoint on the ocis domain was not reachable or returned an empty data set.
I need to understand your setup better. I know, that these things do not happen with https://github.com/owncloud/ocis/tree/master/deployments/examples/ocis_keycloak The challenge is, that it is not that easy to "show me your...
@suse-coder Thanks for adding your valuable experience. The context of this issue is a bit different. Would you be so kind to open a new issue with your backup/restore problem?