difficulties loging in with known

[dissolve]

from @kevinmarks

If I login with known it says "http://Known.kevinmarks.com" does not match the logged in user "http://known.kevinmarks.com/profile/kevinmarks".

[chrisaldrich]

I've had issues in the past with using IndieAuth logins and Known. Sometimes it's finicky and prefers the http://sitename.com/profile/username pattern and won't work with http://sitename.com.

I'll note that I've tried logging in with both:
http://stream.boffosocko.com/profile/chrisaldrich
http://stream.boffosocko.com
and didn't have any problems/issues.
I suspect that for multi-user installations, Known needs the /profile/username addition to distinguish which account to allow publishing to. If I recall OwnYourGram had issues like this in the past if you need advice on what the solution was.

Does Kevin have a multiuser installation? Perhaps he was trying to log in with one account while logged into another?

[kevinmarks]

I have a multiuser installation, yes, but I am logging in as kevinmarks. With other micropub apps (quill, woodwind), logging in with the base URL and being redirected to the user URL works.

…

On Tue, Nov 29, 2016 at 10:56 AM, Chris Aldrich ***@***.***> wrote: <#14 had issues in the past with using IndieAuth logins and Known. Sometimes it's finicky and prefers the http://sitename.com/profile/username pattern and won't work with http://sitename.com. I'll note that I've tried logging in with both: http://stream.boffosocko.com/profile/chrisaldrich http://stream.boffosocko.com and didn't have any problems/issues. I suspect that for multi-user installations, Known needs the /profile/username addition to distinguish which account to allow publishing to. If I recall OwnYourGram had issues like this in the past if you need advice on what the solution was. Does Kevin have a multiuser installation? Perhaps he was trying to log in with one account while logged into another? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#14 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGCwLjB0-m7SNapyuctqvXdEYGSMX2Nks5rDHVWgaJpZM4KzE1_> .

[aaronpk]

I can't find the issue from where this came up in other projects, but I think the conclusion we came to before is this:

You should use whatever comes back from the auth endpoint as long as it's on the same domain as what was entered.

[dissolve]

I've decided i'll add support but only if its on the same domain and the new URL has the same auth endpoint as the original one.