Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Crowd with Azure Active Directory and Guest Users

Hi,

I have Crowd running with Azure Active Directory. We have a small number of organisation accounts (our Exec team) and they can authenticate fine. However, the guests accounts (our members) can't login via Crowd. 

A guest account can login fine to Office 365 groups so that is all fine. The guest users all appear in Office 365 Admin console and Azure AD.

In the Crowd application I use the Test authentication. If I use the Guest foreign user id (email address) it complains that the user is not know, which I understand is the case.

Capture.PNG

When I use the local user id, I don't get the 'does not exist' error but I still get 'Invalid Verification'.

Capture.PNG

Is this meant to work? If I can get the local ID to work then I can manage that (I am updating an old Joomla Crowd plugin and will handle the foreign to local user id translation on the Joomla side. [And yes, ODCC has a nifty script but as an NFP we are using zero cost solutions here].

Thanks

Darryn

1 answer

1 accepted

1 vote
Answer accepted

Hi @Darryn Capes-Davis

Disclaimer: I work for the vendor of the ODCC plugin you mentioned in your post.

Crowd's native Azure AD connector relies upon the ADAL4J library which - as of today - does not support the authentication of external guest users (i.e. not belonging to Azure AD tenants).

On the contrary, the ODCC plugin does not use ADAL4J and hence does support external guest users authentication (and you're right, in that case you can either use the userPrincipalName or the email address as the user's login name).

Thanks @Bruno Vincent. I will get in contact with you regarding ODCC.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

300 views 9 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you