Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: High
Fix Version/s: 4.3.4, Bugfix Release
Affects Version/s: 4.3
Component/s: User Management - Others
Labels:

Introduced in Version:
4.03
Bug Fix Policy:
View Atlassian Server bug fix policy

Under OSuser we had the following doc:

If you get an error message javax.naming.PartialResultException: Unprocessed Continuation Reference(s), try adding <property name="java.naming.referral">follow</property> to the LDAPCredentialsProvider section.

In full LDAP we have a "Follow Referrals" setting (under Advanced Settings) for this, but we need something for "LDAP Authentication" directories.

- - Sort By Name
  - Sort By Date
  - Ascending
  - Descending
  - Thumbnails
  - List

osuser.xml
10/May/2011 8:59 AM
1 kB
tier-0 grump

is blocked by

CONFSERVER-22347 There is no follow referrals option for delegated authentication

Closed

is related to

JRASERVER-24500 Editing the automatically created JIRA Delegated Authentication Directory raises an exception

Closed

CWD-2469 If a user has switched "follow referrals" off, then Crowd should not thorw an exception if AD suggests if follow referrals.

Closed

JRASERVER-24634 Delegated LDAP UI does not include the "Follow Referrals" option

Closed

relates to

JRASERVER-23858 Upgrade path for delegated LDAP locks out internal JIRA users

Closed

mentioned in: Page Loading...; Wiki Page Loading...

(2 mentioned in)

Assignee:: Peter Leschev

Reporter:: Mark Lassau (Inactive)

Votes:: 11 Vote for this issue

Watchers:: 12 Start watching this issue

Created:: 18/Mar/2011 12:53 AM

Updated:: 28/Mar/2019 12:01 AM

Resolved:: 26/May/2011 11:13 PM