Re: Oak 1.5.15 release plan

On 2016-12-01 12:15, Davide Giannella wrote: Hello team, I'm planning to cut Oak 1.5.15 on Monday 5th December. If there are any objections please let me know. Otherwise I will re-schedule any non-resolved issue for the next iteration. Angela, Manfred, is

Re: Oak 1.5.15 release plan

Hi Davide, All blocking issue from my side are resolved now Chetan Mehrotra On Mon, Dec 5, 2016 at 12:39 PM, Chetan Mehrotra wrote: > Hi Davide, > > I have marked OAK-5219 as blocker as I want it to be included in > 1.5.15. It might take max 1 day to resolve this

Re: Oak 1.5.15 release plan

Hi Davide, I have marked OAK-5219 as blocker as I want it to be included in 1.5.15. It might take max 1 day to resolve this issue. Would let you know once I have any further update Chetan Mehrotra On Thu, Dec 1, 2016 at 4:45 PM, Davide Giannella wrote: > Hello team, > > I'm

Re: Oak 1.5.15 release plan

Hi Manfred I don't see how you can 'keep it' for the LDAP case. Please create new Improvement ticket, such that we can look for a proper solution. What you actually wanted to do but which IMO got never explicitly mentioned due to mixing implementation details with the generic sync-stuff:

Re: Oak 1.5.15 release plan

Hi Davide, Angela, Note that this is not an issue with oak-auth-ldap, but rather with oak-auth-external. The ExternalIdentity implementation used by oak-auth-ldap uses the DN as both the id and the principal name, so it's working fine. Other implementations of the external auth mechanism

Re: Oak 1.5.15 release plan

Hi Davide IMO the fix for OAK-5200 is straight forward: 1. revert changes made to DynamicSyncContext: it's here where the bug was introduced. that should be doable today. 2. have a quick discussion on oak-dev on how to deal with the new, exported class ExternalGroupRef which was