Mobile client tokens addon #1115

Closed
very-ape wants to merge 0 commits from develop into develop
very-ape commented 2021-05-18 20:42:20 +02:00 (Migrated from github.com)

One of my members tried to use a mobile client yesterday and discovered my SSO scheme didn't play nicely with mobile clients like Fedilab, DiCa, and Friendiqa, as these clients require a username and password. Rather than create an addon to allow them to use their Keycloak credentials with Friendica (as that would compromise their accounts on every service I run in the event of, say, mobile malware), I wrote an addon to allow the issuance and revocation of secondary credentials for Friendica accounts.

One of my members tried to use a mobile client yesterday and discovered my SSO scheme didn't play nicely with mobile clients like Fedilab, DiCa, and Friendiqa, as these clients require a username and password. Rather than create an addon to allow them to use their Keycloak credentials with Friendica (as that would compromise their accounts on every service I run in the event of, say, mobile malware), I wrote an addon to allow the issuance and revocation of secondary credentials for Friendica accounts.
very-ape commented 2021-05-18 20:43:21 +02:00 (Migrated from github.com)

Alright then. I have no idea why that second CI check is failing. I'll wait for input.

Alright then. I have no idea why that second CI check is failing. I'll wait for input.
MrPetovan commented 2021-05-18 20:44:17 +02:00 (Migrated from github.com)

We are using application passwords for the built-in two-factor authentication feature, is there a way you can leverage the existing feature?

We are using application passwords for the built-in two-factor authentication feature, is there a way you can leverage the existing feature?
very-ape commented 2021-05-18 20:49:04 +02:00 (Migrated from github.com)

I'll familiarize myself with that feature and see if there's some way I can rewrite this addon to use that infrastructure instead. There doesn't seem to be a way to achieve what I'm looking for without some sort of addon, though.

I'll familiarize myself with that feature and see if there's some way I can rewrite this addon to use that infrastructure instead. There doesn't seem to be a way to achieve what I'm looking for without some sort of addon, though.
MrPetovan commented 2021-05-18 20:54:57 +02:00 (Migrated from github.com)

You are right, at the very least the app specific password table can be used instead of the general purpose config table.

You are right, at the very least the app specific password table can be used instead of the general purpose config table.
tobiasd commented 2021-05-18 20:58:02 +02:00 (Migrated from github.com)

Alright then. I have no idea why that second CI check is failing. I'll wait for input.

Ignore it ;-) that test is being worked on and currently it is not working.

> Alright then. I have no idea why that second CI check is failing. I'll wait for input. Ignore it ;-) that test is being worked on and currently it is not working.
very-ape commented 2021-05-18 21:29:35 +02:00 (Migrated from github.com)

Wow, yeah. This is extremely close to what I'm looking for. Mostly the trouble seems UI-related. I'm going to go in a slightly different direction now. Will hopefully have a pair of addons ready for review in a day or two.

Edit: Also, I notice now that I forgot to make sure "token IDs" didn't allow slashes in them, which would've caused problems.

Wow, yeah. This is extremely close to what I'm looking for. Mostly the trouble seems UI-related. I'm going to go in a slightly different direction now. Will _hopefully_ have a pair of addons ready for review in a day or two. Edit: Also, I notice now that I forgot to make sure "token IDs" didn't allow slashes in them, which would've caused problems.
MrPetovan commented 2021-05-18 21:34:04 +02:00 (Migrated from github.com)

Thank you!

Thank you!

Pull request closed

Sign in to join this conversation.
No description provided.