[jira] [Updated] (DIRSTUDIO-1285) Proxied auth leads to wrong DIT/rootDSE being used

[ https://issues.apache.org/jira/browse/DIRSTUDIO-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] brent s. updated DIRSTUDIO-1285: Attachment: enable_base_dn_server.log > Proxied auth leads to wrong DIT/rootDSE being u

[jira] [Updated] (DIRSTUDIO-1285) Proxied auth leads to wrong DIT/rootDSE being used

[ https://issues.apache.org/jira/browse/DIRSTUDIO-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] brent s. updated DIRSTUDIO-1285: Attachment: connect_disconnect.log > Proxied auth leads to wrong DIT/rootDSE being u

[jira] [Commented] (DIRSTUDIO-1285) Proxied auth leads to wrong DIT/rootDSE being used

[ https://issues.apache.org/jira/browse/DIRSTUDIO-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17398275#comment-17398275 ] Stefan Seelmann commented on DIRSTUDIO-1285: bq. Full version string is 2.0.0.v20210213

[jira] [Comment Edited] (DIRSTUDIO-1285) Proxied auth leads to wrong DIT/rootDSE being used

[ https://issues.apache.org/jira/browse/DIRSTUDIO-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17398267#comment-17398267 ] brent s. edited comment on DIRSTUDIO-1285 at 8/12/21, 8:08 PM: --- Full

[jira] [Commented] (DIRSTUDIO-1285) Proxied auth leads to wrong DIT/rootDSE being used

[ https://issues.apache.org/jira/browse/DIRSTUDIO-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17398267#comment-17398267 ] brent s. commented on DIRSTUDIO-1285: - Full version string is *2.0.0.v20210213-M16* according

[jira] [Commented] (DIRSTUDIO-1285) Proxied auth leads to wrong DIT/rootDSE being used

[ https://issues.apache.org/jira/browse/DIRSTUDIO-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17398253#comment-17398253 ] Stefan Seelmann commented on DIRSTUDIO-1285: Which Studio version do you use? (full

[jira] [Created] (DIRSTUDIO-1285) Proxied auth leads to wrong DIT/rootDSE being used

brent s. created DIRSTUDIO-1285: --- Summary: Proxied auth leads to wrong DIT/rootDSE being used Key: DIRSTUDIO-1285 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1285 Project: Directory Studio

[jira] [Commented] (DIRSTUDIO-1280) Studio browser connections to replicated LDAP dont work with Mac OS Big Sur

[ https://issues.apache.org/jira/browse/DIRSTUDIO-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17396467#comment-17396467 ] Sourabh Idoorkar commented on DIRSTUDIO-1280: - Just realised had missed out mentioning

[jira] [Resolved] (DIRAPI-378) Finer-grain timeouts

[ https://issues.apache.org/jira/browse/DIRAPI-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radovan Semancik resolved DIRAPI-378. - Resolution: Fixed > Finer-grain timeouts > > >

[jira] [Commented] (DIRAPI-378) Finer-grain timeouts

[ https://issues.apache.org/jira/browse/DIRAPI-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17391563#comment-17391563 ] Radovan Semancik commented on DIRAPI-378: - Implemented in c2fd0a08f > Finer-grain timeo

[jira] [Created] (DIRAPI-378) Finer-grain timeouts

Radovan Semancik created DIRAPI-378: --- Summary: Finer-grain timeouts Key: DIRAPI-378 URL: https://issues.apache.org/jira/browse/DIRAPI-378 Project: Directory Client API Issue Type

[jira] [Comment Edited] (DIRSTUDIO-1284) Error while executing LDIF - [LDAP result code 53 - unwillingToPerform] - Must supply correct old password to change to new one

[ https://issues.apache.org/jira/browse/DIRSTUDIO-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17389780#comment-17389780 ] Stefan Seelmann edited comment on DIRSTUDIO-1284 at 7/29/21, 9:36 AM

[jira] [Commented] (DIRSTUDIO-1284) Error while executing LDIF - [LDAP result code 53 - unwillingToPerform] - Must supply correct old password to change to new one

[ https://issues.apache.org/jira/browse/DIRSTUDIO-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17389780#comment-17389780 ] Stefan Seelmann commented on DIRSTUDIO-1284: Which LDAP server do you use? Googling

[jira] [Updated] (DIRSTUDIO-1284) Error while executing LDIF - [LDAP result code 53 - unwillingToPerform] - Must supply correct old password to change to new one

[ https://issues.apache.org/jira/browse/DIRSTUDIO-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann updated DIRSTUDIO-1284: --- Attachment: screenshot-1.png > Error while executing LDIF - [LDAP result code

[jira] [Created] (DIRSTUDIO-1284) Error while executing LDIF - [LDAP result code 53 - unwillingToPerform] - Must supply correct old password to change to new one

://issues.apache.org/jira/browse/DIRSTUDIO-1284 Project: Directory Studio Issue Type: Bug Components: studio-ldifeditor Affects Versions: 2.0.0-M17 Environment: Mac OS 11.4, running on a MacBook Pro (16-inch, 2019) Reporter: Katie Golan

[jira] [Updated] (DIRSTUDIO-1280) Studio browser connections to replicated LDAP dont work with Mac OS Big Sur

[ https://issues.apache.org/jira/browse/DIRSTUDIO-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann updated DIRSTUDIO-1280: --- Fix Version/s: 2.0.0-M17 > Studio browser connections to replicated LDAP d

[jira] [Closed] (DIRSTUDIO-1280) Studio browser connections to replicated LDAP dont work with Mac OS Big Sur

[ https://issues.apache.org/jira/browse/DIRSTUDIO-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann closed DIRSTUDIO-1280. -- Resolution: Fixed > Studio browser connections to replicated LDAP dont w

[jira] [Comment Edited] (DIRSTUDIO-1283) Generated update site is broken

[ https://issues.apache.org/jira/browse/DIRSTUDIO-1283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17386678#comment-17386678 ] Stefan Seelmann edited comment on DIRSTUDIO-1283 at 7/24/21, 8:58 AM

[jira] [Commented] (DIRSTUDIO-1283) Generated update site is broken

[ https://issues.apache.org/jira/browse/DIRSTUDIO-1283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17386678#comment-17386678 ] Stefan Seelmann commented on DIRSTUDIO-1283: As a workaround for 2.0.0-M17 release it's

[jira] [Created] (DIRSTUDIO-1283) Generated update site is broken

Stefan Seelmann created DIRSTUDIO-1283: -- Summary: Generated update site is broken Key: DIRSTUDIO-1283 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1283 Project: Directory Studio

[jira] [Comment Edited] (DIRSTUDIO-739) Using 'Quick Search' in the DN editor while editing some object cancels editing and jumps to 'Quick Search' in the main window

[ https://issues.apache.org/jira/browse/DIRSTUDIO-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17385368#comment-17385368 ] Robert Wolf edited comment on DIRSTUDIO-739 at 7/22/21, 10:15 AM

[jira] [Reopened] (DIRSTUDIO-739) Using 'Quick Search' in the DN editor while editing some object cancels editing and jumps to 'Quick Search' in the main window

[ https://issues.apache.org/jira/browse/DIRSTUDIO-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Wolf reopened DIRSTUDIO-739: --- Hello, unfortunately, this bug is back again since a few releases. I wanted to report

[jira] [Created] (FC-298) Load test dependency issue on apache commons pool 2

Shawn McKinney created FC-298: - Summary: Load test dependency issue on apache commons pool 2 Key: FC-298 URL: https://issues.apache.org/jira/browse/FC-298 Project: FORTRESS Issue Type

[jira] [Commented] (DIRSTUDIO-1280) Studio browser connections to replicated LDAP dont work with Mac OS Big Sur

[ https://issues.apache.org/jira/browse/DIRSTUDIO-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17383855#comment-17383855 ] Sourabh Idoorkar commented on DIRSTUDIO-1280: - Thanks a lot for your update [~seelmann

[jira] [Created] (DIRSTUDIO-1282) Don't propose AttribuuteType that are already in the mandatory list when creating an objectClass

Emmanuel Lécharny created DIRSTUDIO-1282: Summary: Don't propose AttribuuteType that are already in the mandatory list when creating an objectClass Key: DIRSTUDIO-1282 URL: https://issues.apache.org/jira

[jira] [Created] (DIRSTUDIO-1281) Make the AttributeTypes selection multi-select for ObjectClass creation

Emmanuel Lécharny created DIRSTUDIO-1281: Summary: Make the AttributeTypes selection multi-select for ObjectClass creation Key: DIRSTUDIO-1281 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1281

[jira] [Commented] (DIRSTUDIO-1280) Studio browser connections to replicated LDAP dont work with Mac OS Big Sur

[ https://issues.apache.org/jira/browse/DIRSTUDIO-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17382757#comment-17382757 ] Stefan Seelmann commented on DIRSTUDIO-1280: Which LDAP servers do you use? If it's

[jira] [Commented] (DIRAPI-281) Unable to connect LDAP server via proxy

[ https://issues.apache.org/jira/browse/DIRAPI-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17381108#comment-17381108 ] Alexandre Aufrere commented on DIRAPI-281: -- We are using the API in complex network environments

[jira] [Resolved] (FC-297) [fortress-rest] Exclude jboss-rmi-api_1.0_spec-1.0.6

[ https://issues.apache.org/jira/browse/FC-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-297. --- Resolution: Fixed > [fortress-rest] Exclude jboss-rmi-api_1.0_spec-1.

[jira] [Created] (FC-297) [fortress-rest] Exclude jboss-rmi-api_1.0_spec-1.0.6

Shawn McKinney created FC-297: - Summary: [fortress-rest] Exclude jboss-rmi-api_1.0_spec-1.0.6 Key: FC-297 URL: https://issues.apache.org/jira/browse/FC-297 Project: FORTRESS Issue Type

[jira] [Resolved] (FC-296) Parameterize Default TLS Protocols

[ https://issues.apache.org/jira/browse/FC-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-296. --- Resolution: Fixed > Parameterize Default TLS Protoc

[jira] [Created] (FC-296) Parameterize Default TLS Protocols

Shawn McKinney created FC-296: - Summary: Parameterize Default TLS Protocols Key: FC-296 URL: https://issues.apache.org/jira/browse/FC-296 Project: FORTRESS Issue Type: Improvement Affects

[jira] [Updated] (FC-283) Remove property files from quickstart doc

[ https://issues.apache.org/jira/browse/FC-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-283: -- Fix Version/s: (was: 3.0.0) 2.0.6 > Remove property files from quickstart

[jira] [Updated] (FC-284) [fortress-core] JDK14 dependency for xml.bind missing

[ https://issues.apache.org/jira/browse/FC-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-284: -- Fix Version/s: (was: 3.0.0-RC1) 2.0.6 > [fortress-core] JDK14 depende

[jira] [Updated] (FC-285) [fortress-core]Infinite loop in property interpolation of ${min.log.conn}: min.log.conn

[ https://issues.apache.org/jira/browse/FC-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-285: -- Fix Version/s: (was: 3.0.0-RC1) 2.0.6 > [fortress-core]Infinite loop in prope

[jira] [Resolved] (FC-286) To Apache Log4j 2

[ https://issues.apache.org/jira/browse/FC-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-286. --- Fix Version/s: (was: 3.0.0-RC1) 2.0.6 Resolution: Fixed > To Apache Lo

[jira] [Resolved] (FC-238) Migrate to LDAP API 2.0

[ https://issues.apache.org/jira/browse/FC-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-238. --- Resolution: Fixed > Migrate to LDAP API 2.0 > --- > >

[jira] [Resolved] (FC-289) [fortress-web] get log4j2 working

[ https://issues.apache.org/jira/browse/FC-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-289. --- Fix Version/s: (was: 3.0.0-RC1) 2.0.6 Resolution: Fixed > [fortress-

[jira] [Commented] (DIRSTUDIO-1280) Studio browser connections to replicated LDAP dont work with Mac OS Big Sur

[ https://issues.apache.org/jira/browse/DIRSTUDIO-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17372303#comment-17372303 ] Sourabh Idoorkar commented on DIRSTUDIO-1280: - OK now that I specifically look

[jira] [Created] (DIRSTUDIO-1280) Studio browser connections to replicated LDAP dont work with Mac OS Big Sur

Sourabh Idoorkar created DIRSTUDIO-1280: --- Summary: Studio browser connections to replicated LDAP dont work with Mac OS Big Sur Key: DIRSTUDIO-1280 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1280

[jira] [Created] (FC-295) Move/Improve RBAC Accelerator Client

Shawn McKinney created FC-295: - Summary: Move/Improve RBAC Accelerator Client Key: FC-295 URL: https://issues.apache.org/jira/browse/FC-295 Project: FORTRESS Issue Type: Improvement Affects

[jira] [Commented] (DIRSERVER-2350) Database corruption

[ https://issues.apache.org/jira/browse/DIRSERVER-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17371575#comment-17371575 ] Stefan Seelmann commented on DIRSERVER-2350: https://directory.apache.org/apacheds

[jira] [Created] (DIRSERVER-2350) Database corruption

Matt Pavlovich created DIRSERVER-2350: - Summary: Database corruption Key: DIRSERVER-2350 URL: https://issues.apache.org/jira/browse/DIRSERVER-2350 Project: Directory ApacheDS Issue Type

[jira] [Resolved] (FC-258) Updating the way FortResponse is served

[ https://issues.apache.org/jira/browse/FC-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-258. --- Resolution: Fixed > Updating the way FortResponse is ser

[jira] [Closed] (FC-258) Updating the way FortResponse is served

[ https://issues.apache.org/jira/browse/FC-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney closed FC-258. - > Updating the way FortResponse is served > --- > >

[jira] [Commented] (FC-262) Add tmeout configuration for connection pools

[ https://issues.apache.org/jira/browse/FC-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17369886#comment-17369886 ] Shawn McKinney commented on FC-262: --- This issue needs a description as to what timeout values are missing

[jira] [Resolved] (FC-291) Support Relax Control

[ https://issues.apache.org/jira/browse/FC-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-291. --- Resolution: Fixed > Support Relax Control > - > >

[jira] [Resolved] (FC-292) User displayName attribute not updated

[ https://issues.apache.org/jira/browse/FC-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-292. --- Resolution: Fixed > User displayName attribute not upda

[jira] [Closed] (FC-244) [fortress-core] builds fail in Java 11

[ https://issues.apache.org/jira/browse/FC-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney closed FC-244. - Resolution: Not A Bug > [fortress-core] builds fail in Java

[jira] [Updated] (FC-293) [fortress-web] CVE-2020-11976

[ https://issues.apache.org/jira/browse/FC-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-293: -- Affects Version/s: (was: 2.0.4) 2.0.5 > [fortress-web] CVE-2020-11

[jira] [Resolved] (FC-293) [fortress-web] CVE-2020-11976

[ https://issues.apache.org/jira/browse/FC-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-293. --- Resolution: Fixed > [fortress-web] CVE-2020-11

[jira] [Closed] (FC-293) [fortress-web] CVE-2020-11976

[ https://issues.apache.org/jira/browse/FC-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney closed FC-293. - > [fortress-web] CVE-2020-11976 > - > >

[jira] [Updated] (FC-293) [fortress-web] CVE-2020-11976

[ https://issues.apache.org/jira/browse/FC-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-293: -- Affects Version/s: 2.0.4 > [fortress-web] CVE-2020-11

[jira] [Updated] (FC-291) Support Relax Control

[ https://issues.apache.org/jira/browse/FC-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-291: -- Fix Version/s: (was: 2.0.4) 2.0.6 > Support Relax Cont

[jira] [Reopened] (FC-293) [fortress-web] CVE-2020-11976

[ https://issues.apache.org/jira/browse/FC-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney reopened FC-293: --- Assignee: Shawn McKinney > [fortress-web] CVE-2020-11

[jira] [Updated] (FC-293) [fortress-web] CVE-2020-11976

[ https://issues.apache.org/jira/browse/FC-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-293: -- Fix Version/s: 2.0.6 > [fortress-web] CVE-2020-11

[jira] [Resolved] (DIRAPI-377) Add LDAP Relax Rules Control

[ https://issues.apache.org/jira/browse/DIRAPI-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann resolved DIRAPI-377. Resolution: Fixed https://github.com/apache/directory-ldap-api/commit

[jira] [Created] (DIRAPI-377) Add LDAP Relax Rules Control

Stefan Seelmann created DIRAPI-377: -- Summary: Add LDAP Relax Rules Control Key: DIRAPI-377 URL: https://issues.apache.org/jira/browse/DIRAPI-377 Project: Directory Client API Issue Type

[jira] [Commented] (FC-238) Migrate to LDAP API 2.0

[ https://issues.apache.org/jira/browse/FC-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17369035#comment-17369035 ] Shawn McKinney commented on FC-238: --- 4. RBAC Accelerator Extended Ops (LdapConnectionProvider) change

[jira] [Commented] (FC-238) Migrate to LDAP API 2.0

[ https://issues.apache.org/jira/browse/FC-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17369014#comment-17369014 ] Shawn McKinney commented on FC-238: --- 2. Relax Control (LdapDataProvider) Two part solution: a. add

[jira] [Commented] (FC-238) Migrate to LDAP API 2.0

[ https://issues.apache.org/jira/browse/FC-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17369008#comment-17369008 ] Shawn McKinney commented on FC-238: --- 3. here's how to retrieve the control: protected

[jira] [Resolved] (DIRAPI-376) Change getRootDse() to return all user and operational attibutes

[ https://issues.apache.org/jira/browse/DIRAPI-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann resolved DIRAPI-376. Resolution: Fixed > Change getRootDse() to return all user and operational attibu

[jira] [Commented] (DIRAPI-376) Change getRootDse() to return all user and operational attibutes

[ https://issues.apache.org/jira/browse/DIRAPI-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17368413#comment-17368413 ] Stefan Seelmann commented on DIRAPI-376: https://github.com/apache/directory-ldap-api/commit

[jira] [Updated] (DIRAPI-376) Change getRootDse() to return all user and operational attibutes

[ https://issues.apache.org/jira/browse/DIRAPI-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann updated DIRAPI-376: --- Component/s: (was: ldap) Fix Version/s: (was: 2.0.3

[jira] [Created] (DIRSERVER-2349) Change getRootDse() to return all user and operational attibutes

Stefan Seelmann created DIRSERVER-2349: -- Summary: Change getRootDse() to return all user and operational attibutes Key: DIRSERVER-2349 URL: https://issues.apache.org/jira/browse/DIRSERVER-2349

[jira] [Commented] (FC-238) Migrate to LDAP API 2.0

[ https://issues.apache.org/jira/browse/FC-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17368407#comment-17368407 ] Shawn McKinney commented on FC-238: --- 3. PW Policy Control (LdapDataProvider) Follow this test example

[jira] [Comment Edited] (FC-238) Migrate to LDAP API 2.0

[ https://issues.apache.org/jira/browse/FC-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17367342#comment-17367342 ] Shawn McKinney edited comment on FC-238 at 6/22/21, 4:04 PM: - Renewing this work

[jira] [Commented] (FC-238) Migrate to LDAP API 2.0

[ https://issues.apache.org/jira/browse/FC-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17367342#comment-17367342 ] Shawn McKinney commented on FC-238: --- Renewing this work.  Here are the problem areas:   1. LDAP

[jira] [Updated] (FC-238) Migrate to LDAP API 2.0

[ https://issues.apache.org/jira/browse/FC-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-238: -- Fix Version/s: (was: 3.0.0-RC1) 2.0.6 > Migrate to LDAP API

[jira] [Assigned] (FC-238) Migrate to LDAP API 2.0

[ https://issues.apache.org/jira/browse/FC-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney reassigned FC-238: - Assignee: Shawn McKinney (was: Emmanuel Lécharny) > Migrate to LDAP API

[jira] [Updated] (FC-294) combine jmeter load profiles

[ https://issues.apache.org/jira/browse/FC-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-294: -- Description: Currently 9 maven profiles for load testing. Combine into one or at most two.   Current

[jira] [Resolved] (FC-294) combine jmeter load profiles

[ https://issues.apache.org/jira/browse/FC-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-294. --- Resolution: Fixed > combine jmeter load profiles > > >

[jira] [Updated] (DIRSTUDIO-1279) Show SSL/TLS connection info and certificates

[ https://issues.apache.org/jira/browse/DIRSTUDIO-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann updated DIRSTUDIO-1279: --- Description: Add a button to view the used protcol, cipher suite

[jira] [Commented] (DIRSTUDIO-1279) Show SSL/TLS connection info and certificates

[ https://issues.apache.org/jira/browse/DIRSTUDIO-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17367007#comment-17367007 ] Stefan Seelmann commented on DIRSTUDIO-1279: https://github.com/apache/directory-studio

[jira] [Resolved] (DIRSTUDIO-1011) ApacheStudio sends SSLv2 Client Hello

[ https://issues.apache.org/jira/browse/DIRSTUDIO-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann resolved DIRSTUDIO-1011. Resolution: Done Tested with a current Java 11.0.11 and 17-ea, Studio sends

[jira] [Resolved] (DIRAPI-375) Add TLSv1.3 to default protocols

[ https://issues.apache.org/jira/browse/DIRAPI-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann resolved DIRAPI-375. Resolution: Fixed https://github.com/apache/directory-ldap-api/commit

[jira] [Created] (DIRAPI-375) Add TLSv1.3 to default protocols

Stefan Seelmann created DIRAPI-375: -- Summary: Add TLSv1.3 to default protocols Key: DIRAPI-375 URL: https://issues.apache.org/jira/browse/DIRAPI-375 Project: Directory Client API Issue Type

[jira] [Resolved] (DIRSTUDIO-761) GSSAPI Authentication fails when using ADS LDAP Client API

[ https://issues.apache.org/jira/browse/DIRSTUDIO-761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann resolved DIRSTUDIO-761. --- Resolution: Fixed This has been fixed in scope of the linked issues and tests

[jira] [Commented] (DIRSTUDIO-1219) Directory Studio doesn't StartTLS before authenticating

[ https://issues.apache.org/jira/browse/DIRSTUDIO-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17366162#comment-17366162 ] Stefan Seelmann commented on DIRSTUDIO-1219: Changed usage of {{useTls}} flag in the LDAP

[jira] [Resolved] (DIRSTUDIO-1219) Directory Studio doesn't StartTLS before authenticating

[ https://issues.apache.org/jira/browse/DIRSTUDIO-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann resolved DIRSTUDIO-1219. Resolution: Fixed > Directory Studio doesn't StartTLS before authenticat

[jira] [Commented] (DIRSTUDIO-1220) Directory Studio doesn't use the SASL confidentiality layer after negotiating its use

[ https://issues.apache.org/jira/browse/DIRSTUDIO-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17366138#comment-17366138 ] Stefan Seelmann commented on DIRSTUDIO-1220: Implemented SASL security layer in the LDAP

[jira] [Resolved] (DIRSTUDIO-1220) Directory Studio doesn't use the SASL confidentiality layer after negotiating its use

[ https://issues.apache.org/jira/browse/DIRSTUDIO-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann resolved DIRSTUDIO-1220. Assignee: Stefan Seelmann Resolution: Fixed > Directory Studio does

[jira] [Resolved] (DIRSERVER-1670) DIGEST-MD5 authentication mechanism must support encryption

[ https://issues.apache.org/jira/browse/DIRSERVER-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann resolved DIRSERVER-1670. Fix Version/s: (was: 2.0.0-RC1) 2.0.0.AM27

[jira] [Resolved] (DIRSERVER-1632) Setting SASL QoP to 'auth-int' or 'auth-conf' while connecting using the LDAP API fails and throws a decoder exception

[ https://issues.apache.org/jira/browse/DIRSERVER-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann resolved DIRSERVER-1632. Resolution: Fixed > Setting SASL QoP to 'auth-int' or 'auth-conf' wh

[jira] [Commented] (DIRSERVER-1632) Setting SASL QoP to 'auth-int' or 'auth-conf' while connecting using the LDAP API fails and throws a decoder exception

[ https://issues.apache.org/jira/browse/DIRSERVER-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17366127#comment-17366127 ] Stefan Seelmann commented on DIRSERVER-1632: Added additional tests using openldap

[jira] [Commented] (DIRSERVER-1632) Setting SASL QoP to 'auth-int' or 'auth-conf' while connecting using the LDAP API fails and throws a decoder exception

[ https://issues.apache.org/jira/browse/DIRSERVER-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17366109#comment-17366109 ] Stefan Seelmann commented on DIRSERVER-1632: https://github.com/apache/directory-server

[jira] [Updated] (DIRSERVER-1632) Setting SASL QoP to 'auth-int' or 'auth-conf' while connecting using the LDAP API fails and throws a decoder exception

[ https://issues.apache.org/jira/browse/DIRSERVER-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann updated DIRSERVER-1632: --- Fix Version/s: (was: 2.0.0-RC1) 2.0.0.AM27 > Setting S

[jira] [Resolved] (DIRAPI-373) Implement SASL integrity and confidentiality layer

[ https://issues.apache.org/jira/browse/DIRAPI-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann resolved DIRAPI-373. Resolution: Fixed > Implement SASL integrity and confidentiality la

[jira] [Resolved] (DIRAPI-374) Consistify LdapConnectionConfig useTls and useSsl flags

[ https://issues.apache.org/jira/browse/DIRAPI-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann resolved DIRAPI-374. Resolution: Fixed > Consistify LdapConnectionConfig useTls and useSsl fl

[jira] [Commented] (DIRAPI-374) Consistify LdapConnectionConfig useTls and useSsl flags

[ https://issues.apache.org/jira/browse/DIRAPI-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17366017#comment-17366017 ] Stefan Seelmann commented on DIRAPI-374: https://github.com/apache/directory-ldap-api/commit

[jira] [Created] (DIRAPI-374) Consistify LdapConnectionConfig useTls and useSsl flags

Stefan Seelmann created DIRAPI-374: -- Summary: Consistify LdapConnectionConfig useTls and useSsl flags Key: DIRAPI-374 URL: https://issues.apache.org/jira/browse/DIRAPI-374 Project: Directory Client

[jira] [Commented] (DIRAPI-373) Implement SASL integrity and confidentiality layer

[ https://issues.apache.org/jira/browse/DIRAPI-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17365666#comment-17365666 ] Stefan Seelmann commented on DIRAPI-373: https://github.com/apache/directory-ldap-api/commit

[jira] [Created] (DIRAPI-373) Implement SASL integrity and confidentiality layer

Stefan Seelmann created DIRAPI-373: -- Summary: Implement SASL integrity and confidentiality layer Key: DIRAPI-373 URL: https://issues.apache.org/jira/browse/DIRAPI-373 Project: Directory Client API

[jira] [Created] (FC-294) combine jmeter load profiles

Shawn McKinney created FC-294: - Summary: combine jmeter load profiles Key: FC-294 URL: https://issues.apache.org/jira/browse/FC-294 Project: FORTRESS Issue Type: Improvement Affects Versions

[jira] [Updated] (DIRSTUDIO-1220) Directory Studio doesn't use the SASL confidentiality layer after negotiating its use

[ https://issues.apache.org/jira/browse/DIRSTUDIO-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann updated DIRSTUDIO-1220: --- Fix Version/s: 2.0.0-M17 > Directory Studio doesn't use the SASL confidential

[jira] [Updated] (DIRSTUDIO-761) GSSAPI Authentication fails when using ADS LDAP Client API

[ https://issues.apache.org/jira/browse/DIRSTUDIO-761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann updated DIRSTUDIO-761: -- Fix Version/s: 2.0.0-M17 > GSSAPI Authentication fails when using ADS LDAP Cli

[jira] [Commented] (DIRSTUDIO-1279) Show connection certificate

[ https://issues.apache.org/jira/browse/DIRSTUDIO-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355915#comment-17355915 ] Stefan Seelmann commented on DIRSTUDIO-1279: Added here: https://github.com/apache

[jira] [Resolved] (DIRSTUDIO-1279) Show connection certificate

[ https://issues.apache.org/jira/browse/DIRSTUDIO-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann resolved DIRSTUDIO-1279. Resolution: Fixed > Show connection certific

[jira] [Commented] (DIRAPI-361) LDAP Protocol error if password is expiring

[ https://issues.apache.org/jira/browse/DIRAPI-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355201#comment-17355201 ] Emmanuel Lécharny commented on DIRAPI-361: -- Yes, obviously, if the server does not support

[jira] [Commented] (DIRAPI-361) LDAP Protocol error if password is expiring

[ https://issues.apache.org/jira/browse/DIRAPI-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355020#comment-17355020 ] Gunics Balázs commented on DIRAPI-361: -- Thank you [~elecharny], I wasn't able to figure out

<    5   6   7   8   9   10   11   12   13   14   >