Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reworded warning for clarity #6620

Merged
merged 8 commits into from
Nov 6, 2024
Merged

Reworded warning for clarity #6620

merged 8 commits into from
Nov 6, 2024

Conversation

eshanrnh
Copy link
Contributor

@eshanrnh eshanrnh commented Nov 5, 2024

Description

As per issue #6586, updated the note to specify that the conflict with Entra ID only applies to backoffice logins, not member logins. Added a line about the upcoming feature (WIP) which might remove this limitation.

Type of suggestion

  • Typo/grammar fix
  • Updated outdated content
  • New content
  • Updates related to a new version
  • Other

Product & version (if relevant)

CMS v14.

Deadline (if relevant)

Anytime

Copy link
Contributor

@sofietoft sofietoft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great @eshanrnh !

I'm not sure about the note about the upcoming feature on Cloud.
It's a temporary note that we will somehow need to keep track of, to make sure we remove it once the feature is actually launched 🤔

@eshanrnh
Copy link
Contributor Author

eshanrnh commented Nov 5, 2024

I removed the line about the upcoming feature but I believe even the Note will have to be removed once the feature is released since then Entra ID will be compatible with backoffice users as well.

@sofietoft
Copy link
Contributor

I removed the line about the upcoming feature but I believe even the Note will have to be removed once the feature is released since then Entra ID will be compatible with backoffice users as well.

Yes, that's a good point!
Let's talk about how we can keep track of this somehow, so we remember to remove it once the feature is out 💪

@eshanrnh eshanrnh merged commit f81a463 into main Nov 6, 2024
7 checks passed
@eshanrnh eshanrnh deleted the eshanrnh-patch-2 branch November 21, 2024 10:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants