Status after upgrading to 0.2.29: User story of a distant login

I've upgraded test1 & test2 instance with a proper federated configuration.

My account is hosted on test1.

If I login on test2, here's what I tried:

• With jbpasquier@api.test1.startinblox.com: {"error": "cannot_get_provider_info", "error_description": "Cannot get provider informations"} #44 (closed) #40 (closed)
• With https://api.test1.startinblox.com/users/jbpasquier/: {"error": "cannot_get_provider_info", "error_description": "Cannot get provider informations"} #45
• With only https://api.test1.startinblox.com: I was redirected properly to test1 login page!

After a login on test1, it asked me for allowing to share my email and basic profile ; but with an ugly css list. #46 (closed)

Then I landed on Sorry, we couldn't find a page to redirect you to. Please navigate to your preferred application manually. #42

So I get to the app front-end and press login to update my default-redirect-uri. #42

Now, I'm logged in on test2 with my account on test1 properly! :)

But (:'(), I appear two times on left menu, because local containers still serve distant resources - they should not. djangoldp#210 (closed)

I started a new session, now that my user is linked on test2. I press login from front-end then use the 3rd method described here. I didn't get the permission ask (Which is right! :)) but I landed on Sorry, we couldn't find a page to redirect you to. Please navigate to your preferred application manually and had to start over the login to get properly redirected. Also I faced framework/sib-core#589 (closed)

From here, I can update one of my circle information properly! But, I get no chat anywhere. https://git.happy-dev.fr/startinblox/prosody/custom-prosody-modules/issues/10

Error from Converse: 2020-03-17T12:07:41.504Z DEBUG: Status changed to: AUTHFAIL

Error from Prosody: (A bit weird about 404, because I can reach it from here)

Mar 17 12:10:25 test1.startinblox.com:auth_oauthbearer  debug   Testing signed OAuth2 for user jbpasquier at realm test1.startinblox.com
Mar 17 12:10:25 test1.startinblox.com:auth_oauthbearer  debug   The URL is:  http://api.test1.startinblox.com/check-user
Mar 17 12:10:25 test1.startinblox.com:auth_oauthbearer  debug   OAuth provider returned status code: 404
Mar 17 12:10:25 test1.startinblox.com:auth_oauthbearer  warn    Auth failed. Invalid username/password or misconfiguration.
Mar 17 12:10:25 test1.startinblox.com:saslauth  debug   sasl reply: <failure xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><not-authorized/><text>Unable to authorize you with the authentication credentials you&apos;ve sent.</text></failure>

I created a circle on test2, with my test1 user as an owner. I worked fine. But I don't see it on left menu: Missing backlinks here to have it works. djangoldp#196 (closed)

I can't add users from test2 to my circle on test1, request got stuck with no answer. djangoldp-circle#2 (closed)

After few minutes (~15), I refreshed, surprise here: I was logged out from test2 (but not from test1). Had a second try, and still face that. framework/sib-auth#32

--

@sylvain @balessan @calummackervoy @matthieu @MattJ @alexbourlier Here is the current status regarding federation with latest fixes from Calum. I'll make separated issues for everything that is in bold. Some part are frontend (sib-auth, sib-core), some backend (prosody and djangoldp).