Hi Ruwan,
Sorry if I didn't explain it clearly.
What I meant was ...
The PKCE feature was shipped as an update to IS 5.3.0 initially and it had
a schema change.
So the code was added in a backward compatible way.
But since 5.5.0 is a minor release we can get rid of the backward
compatible code since the migration is any way there. (if time permits :-) )
On Sun, Feb 18, 2018 at 6:06 PM, Ruwan Abeykoon <ruw...@wso2.com> wrote:
> Hi Rushmin,
> Need clarification, do you mean the table not exist in DB case? DB scripts
> can be created with migration script.
>
> Cheers,
> Ruwan
>
>
> On Sun, Feb 18, 2018 at 5:12 PM, Rushmin Fernando <rush...@wso2.com>
> wrote:
>
>>
>> AFAIK this code was introduced to protect backward compatibility while
>> introducing PKCE support sometime back.
>>
>> We still see the following log.
>>
>> INFO {org.wso2.carbon.identity.oauth2.internal.OAuth2ServiceComponent}
>> - PKCE Support enabled.
>>
>> Do we still need that code (not only the log but the backward
>> compatibility code too)?
>>
>>
>> --
>> *Best Regards*
>>
>> *Rushmin Fernando*
>> *Technical Lead*
>>
>> WSO2 Inc. <http://wso2.com/> - Lean . Enterprise . Middleware
>>
>> mobile : +94775615183
>>
>>
>>
>
>
> --
>
> *Ruwan Abeykoon*
> *Associate Director/Architect**,*
> *WSO2, Inc. http://wso2.com <https://wso2.com/signature> *
> *lean.enterprise.middleware.*
>
>
--
*Best Regards*
*Rushmin Fernando*
*Technical Lead*
WSO2 Inc. <http://wso2.com/> - Lean . Enterprise . Middleware
mobile : +94775615183
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
