No longer able to update Crowd User Directory in Bitbucket

[Penta Research Inc]

I setup Crowd and Bitbucket.  Everything was great.  My admin account authenticated.  I went to deploy it to my users and they were not able to authenticate.  

When I sync the Directory it succeeds.  Even though Bitbucket thinks it succeeded when I look at the group members they have not updated.

When I test the directory with my admin account I get Successes all the way

When I test the directory with one of their accounts I get All successes until I get to the bottom and get 

Test user can authenticate : FailedAccount with name <user> failed to authenticate

When I update an active directory group in active directory crowd sees the update but bitbucket does not.  It is working properly for jira, confluence, and crucible

The only thing I see in the debug log that hints that there is a problem is this error message:

2019-06-26 13:35:50,101 DEBUG [http-nio-7990-exec-9] @CQKM4Ux815x1343x0 127.0.0.1,127.0.0.1 "GET /rest/capabilities/navigation HTTP/1.1" c.a.b.i.c.s.CrowdSsoAuthenticationHandler Skipping Crowd SSO as it is not enabled
2019-06-26 13:35:50,101 DEBUG [http-nio-7990-exec-9] @CQKM4Ux815x1343x0 127.0.0.1,127.0.0.1 "GET /rest/capabilities/navigation HTTP/1.1" c.a.s.i.i18n.PluginI18nService No values found in any valid locale for key ProviderManager.providerNotFound and locales [en_US, en]

We are not using SSO as we are using starter licenses for both Crowd and Bitbucket.

I have tried restarting the bitbucket service, logging into a bitbucket local account and disabling the crowd directory, then re-enabling it.  I have look through the logs and tried my google-fu but so far I'm coming up with nothing.

Any help would be appreciated.

Follow up 2019-06-26:

After a reboot of the server the syncing of Active Directory groups began working again for bitbucket however new authorized users still get the error message "Invalid username or password" when trying to sign in and "Test user can authenticate : FailedAccount with name <user> failed to authenticate" when testing the Crowd User Directory inside bitbucket.  

We are running version 6.2.

Follow up 2019-06-27:

I have upgraded to version 6.4 with no change.  I am starting to wonder if the issue is that when initially set it up bitbucket used the default internal database.  Right after install realized this and migrated from the internal database to postgres.  

[Penta Research Inc]

Apparently I had put the bamboo credentials for crowd in the bitbucket crowd connector.  I think it was working properly until I finished the bamboo configuration.

[Prasanth]

Hi Team

As per the latest the update, I understand that the groups and users are synchronized to Bitbucket, am I right?

I tried to reproduce this with 6.4 Bitbucket and Crowd 3.4, I couldn't so it appears to be a configuration issue.

Please check the following:

- Make sure the Bitbucket application is associated with the right Directory configuration in Crowd. i.e. Applications->Select the Bitbucket Application that you Configured->Navigate to to the Directories and Groups tab and check the right directory configuration is selected there.

- Also check the "Who can authenticate" and "Automatically assigned to" groups for that directory and make sure right groups are picked up there.

In Bitbucket Server, check the Global Permissions page and make sure the right group is selected for the "Group access"

Hope this helps.

Regards

Prasanth Thaikkalloor

[Penta Research Inc]

I found the issue late last night.  Apparently I had put the bamboo credentials for crowd in the bitbucket crowd connector.  I think it was working properly until I finished the bamboo configuration.

Thanks for the reply,

-Kirk