If a user only has an oidc provider as active first factor credential, an disabled unlink node should be send

[simon-wirths-uninow]

Preflight checklist

• [X] I could not find a solution in the existing issues, docs, nor discussions.
• [X] I agree to follow this project's Code of Conduct.
• [X] I have read and am following this repository's Contribution Guidelines.
• [ ] I have joined the Ory Community Slack.
• [ ] I am signed up to the Ory Security Patch Newsletter.

Ory Network Project

No response

Describe your problem

If a user only has an oidc provider as active first factor credential you get absolutely no feedback why you can not unlink your social account. This is really confusing for the user.

Describe your ideal solution

When the settings flow checks if there is more then one first factor credential for a user, it could also check if its a linked social account if there is only one. It the should create a disabled unlink node maybe with a message why unlinking is not possible at the moment.

Workarounds or alternatives

an alternative would be to check separately with kratos if the user has an linked account and then show a disabled button without a ui node. also you could show a hint all the time that you need to set a password to unlink.

Version

1.0.0

Additional Context

No response

[alnr]

I think that would be a useful improvement.

[github-actions[bot]]

Hello contributors!

I am marking this issue as stale as it has not received any engagement from the community or maintainers for a year. That does not imply that the issue has no merit! If you feel strongly about this issue

• open a PR referencing and resolving the issue;
• leave a comment on it and discuss ideas on how you could contribute towards resolving it;
• leave a comment and describe in detail why this issue is critical for your use case;
• open a new issue with updated details and a plan for resolving the issue.

Throughout its lifetime, Ory has received over 10.000 issues and PRs. To sustain that growth, we need to prioritize and focus on issues that are important to the community. A good indication of importance, and thus priority, is activity on a topic.

Unfortunately, burnout has become a topic of concern amongst open-source projects.

It can lead to severe personal and health issues as well as opening catastrophic attack vectors.

The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.

If this issue was marked as stale erroneously you can exempt it by adding the backlog label, assigning someone, or setting a milestone for it.

Thank you for your understanding and to anyone who participated in the conversation! And as written above, please do participate in the conversation if this topic is important to you!

Thank you 🙏✌️