[keycloak-dev] code freeze at end of day today

[Marek Posolda]

So finally I seems to have a fix for MSSSQL and commited it. It 
complained about Integer.MAX_VALUE in the query limit:-)

Oracle is fixed as well, it complained again about too long identifier 
(there is limit for tableName, columnName and indexName to be max 30 
characters).

I am also not enjoying testing with databases much. I am using jenkins 
QA lab to access various databases and LDAP servers and I am able to 
debug it locally with being connected to remote DB in QA lab, but 
connection is quite slow and running single unit test took couple of 
minutes. So it's a bit painfull...

For LDAP, I would need to update the automated tests for changes related 
to FederationProvider vs. AuthenticationProviders and also fix some 
stuff to setup automated test for Active Directory, which doesn't work 
correctly ATM, so I am testing it manually.

I've tried to reproduce issue KEYCLOAK-602 reported by aerogear guys, 
but wasn't successful. For me Keycloak WAR distribution deployed on EAP 
6.3.0.Beta worked with MySQL 5.5.

I will try to update docs later in the evening (won't do more commits to 
sources). Besides that there are some portal blockers, I am supposed to 
look at, so not sure how I would be able to help you more with release 
testing tomorrow:-(

Marek

On 5.8.2014 16:09, Bill Burke wrote:
> Thank god or you...I absolutely hate doing testing on different 
> databases (and LDAP servers for that matter).  Do you have an easy way 
> to set up testing environments for these different dbs?
>
> On 8/5/2014 9:09 AM, Marek Posolda wrote:
>> ok, merged. Found that oracle and mssql are broken, so looking at those
>> now:-(
>>
>> I seem to have fix for oracle already, need to test a bit more and then
>> look at mssql...
>>
>> On 5.8.2014 15:02, Bill Burke wrote:
>>> YOu find bugs, typos, etc.  Fix them, you have until lunch my time
>>> (eastern USA).
>>>
>>> On 8/5/2014 8:43 AM, Marek Posolda wrote:
>>>> Added another commit for deleting of users on mongo . Both are one
>>>> liners and I hope they are quite safe to be included though.
>>>>
>>>> Marek
>>>>
>>>> On 5.8.2014 13:33, Marek Posolda wrote:
>>>>> On 5.8.2014 13:04, Marek Posolda wrote:
>>>>>>>> * The semantics of "searchForUser" is a bit different for
>>>>>>>> >>FederationProviders and our model implementations. For example,
>>>>>>>> if you
>>>>>>>> >>have user "John Doe" and you search for "ohn Do" in admin
>>>>>>>> console, then
>>>>>>>> >>both JPA and Mongo local providers will return you "John Doe"
>>>>>>>> as they
>>>>>>>> >>add % at the beginning/end. However federation providers are
>>>>>>>> looking
>>>>>>>> >>exactly for FirstName: "ohn" , LastName: "Do", so if "John Doe"
>>>>>>>> exists
>>>>>>>> >>in LDAP, he won't be returned.
>>>>>>>> >>
>>>>>>> >Can we do anything about that?  Does LDAP have a "like"?
>>>>>> yes, LDAP has * . Workaround, which works for me is to put directly
>>>>>> search string like:*ohn Do*   into admin console, but this is not
>>>>>> pretty package org.keycloak.models;
>>>>>>
>>>>>> and is LDAP specific though.
>>>>> btv. Found a typo when test ldap searching. Not sure if it's ok to
>>>>> commit at this stage, so just send PR for that
>>>>> https://github.com/keycloak/keycloak/pull/590 .
>>>>>
>>>>> Marek
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> keycloak-dev mailing list
>>>>> keycloak-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>>>>
>>>
>>
>