Hi Lakmali,Lakshman,

The above issue is due to the following reason.

authenticationendpoint webapp was updated between Alpha2 and Alpha3. So
when we moved to the Alpha3 pack, we did not clean the SVN location.
Therefore it was looking for the webapp provided with Alpha3 pack on the
startup but it was synched with previous version of the webapp via svn.
Cleaning the SVN resolved this particular issue.

Cheers,
Pubudu.

Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

On Mon, Dec 7, 2015 at 7:40 PM, Lakmali Baminiwatta <lakm...@wso2.com>
wrote:

>
>
> On 7 December 2015 at 19:06, Pubudu Priyashan <pubu...@wso2.com> wrote:
>
>> Hey Nuwan,
>>
>> Looks like the root cause for this issue [1] is, due to the internal
>> patch changes we tested with in Alpha2 pack while debugging the LDAP
>> connectivity issue. Can you please take a look and make the necessary
>> changes? Currently this blocks us from testing in cluster due to user not
>> being able to generate keys since gateway cluster is broken.
>>
>> Please let me know if you require any further information. Thanks.
>>
>
> As per the offline discussion had with Pubudu, this looks like due to SVN
> having old authentication web app. As discussed, let's clean the SVN and
> try with the artifacts of the latest pack's deployment directory.
>
> Thanks,
> Lakmali
>
>
>
>> [1] https://wso2.org/jira/browse/APIMANAGER-4358
>>
>> Cheers,
>> Pubudu D.P
>> Senior Software Engineer - QA Team | WSO2 inc.
>> Mobile : +94775464547
>>
>> _______________________________________________
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Lakmali Baminiwatta
> Senior Software Engineer
> WSO2, Inc.: http://wso2.com
> lean.enterprise.middleware
> mobile:  +94 71 2335936
> blog : lakmali.com
>
>
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to