Hi, On Tue, Oct 31, 2017 at 8:20 PM, Prabath Siriwardena <prab...@wso2.com> wrote:
> IIRC TOKEN_ID is how you uniquely refer an access token from other places > - and CODE_ID is how you refer an authorization code uniquely from other > places... > Yes, with the option we have to encrypt and store access tokens and authorization codes, ACCESS_TOKEN and CODE columns need more length. Hence using those as primary keys and then making foreign key reference from other tables to exact values is not convenient and won't be correct to store these sensitive values in multiple places. > > Thanks & regards, > -Prabath > > On Mon, Oct 30, 2017 at 6:31 PM, Sagara Gunathunga <sag...@wso2.com> > wrote: > >> Can someone explain the exact design goals of following two columns on >> identity DB ? >> >> 1. "TOKEN_ID" on IDN_OAUTH2_ACCESS_TOKEN >> >> 2. "CODE_ID " on IDN_OAUTH2_AUTHORIZATION_CODE >> >> >> >> Thanks ! >> -- >> Sagara Gunathunga >> >> Director; WSO2, Inc.; http://wso2.com >> V.P Apache Web Services; http://ws.apache.org/ >> Linkedin; http://www.linkedin.com/in/ssagara >> Blog ; http://ssagara.blogspot.com >> Mobile : +9471 <+94%2071%20565%209887>2149951 >> >> > > > -- > Thanks & Regards, > Prabath > > Twitter : @prabath > LinkedIn : http://www.linkedin.com/in/prabathsiriwardena > > Mobile : +1 650 625 7950 <+1%20650-625-7950> > > http://facilelogin.com > > _______________________________________________ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Pushpalanka. -- Pushpalanka Jayawardhana, B.Sc.Eng.(Hons). Senior Software Engineer, WSO2 Lanka (pvt) Ltd; wso2.com/ Mobile: +94779716248 Blog: pushpalankajaya.blogspot.com/ | LinkedIn: lk.linkedin.com/in/pushpalanka/ | Twitter: @pushpalanka
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev