Repository navigation
Improve UX of adding a third party app as trusted #1142
Description
Activity
This makes sense. I'll be sure to try to implement this feature in the new idp.
Yeah, we need some cross-dependency there because it means the UI of the IDP needs to trigger a change on the pod.
Ah, that's very true. This would require a whole new dimension where the IDP knows all the pods that a user has, and update each one of them. On top of that, the UI isn't just as simple as "grant access to an app." It would be "Grant access to an app for all of my pods... this one pod... everything excluding this pod?"
No, there is only one profile per user, even if there are multiple
pim:storagepods. You find the user's profile by dereferencing their webid, and that's where their list of trusted apps is. In theory, the user's profile doesn't even have to be on their pod, it could also be generated dynamically from the profile information stored in an organization's LDAP server.Reacted by Arne HasselTo inform people following this issue: @jaxoncreed are working on implementing a solution that would allow users to grant access to application as part of the login process if a redirect URL is present and the profile the user tries to authenticate with haven't granted access to application from before and trustedOrigin is set to true for the server.
I'm working on a text that explains what this is about for people uncertain what this part of the login form means.
- added a commit that references this issue
on May 8, 2019
Current UX with NSS 5 for using a third-party webapp:
Proposal: add a checkbox that makes it easier to add an app as trusted, as part of the login flow. With this, it would become: