+1 for APPMSESSIONID On Tue, Jun 28, 2016 at 2:23 PM, Ruwan Abeykoon <[email protected]> wrote:
> +1 APPMSESSIONID, yes "appmSamlSsoTokenId" looks ugly. > > Do we plan to support multiple authentication mechanisms per single > deployment? or is this going to be systemwide config? > > Cheers, > Ruwan > > On Tue, Jun 28, 2016 at 2:12 PM, Dinusha Senanayaka <[email protected]> > wrote: > >> +1 for having it as APPMSESSIONID. There are few places in the code we do >> some functionalities by getting this cookie value. We have to change those >> places and test properly. >> >> Regards, >> Dinusha. >> >> On Tue, Jun 28, 2016 at 2:07 PM, Rushmin Fernando <[email protected]> >> wrote: >> >>> >>> I suggest that we should do the aforementioned change. >>> >>> *Reason* >>> >>> Even though we use SAML as the authentication mechanism in the gateway >>> as of now, we might use different authentication mechanisms in near future. >>> And session handling should be independent of authentication mechanism. >>> >>> So binding the name of the cookie to 'SAML' is ugly >>> >>> WDYT ? >>> >>> >>> >>> -- >>> *Best Regards* >>> >>> *Rushmin Fernando* >>> *Technical Lead* >>> >>> WSO2 Inc. <http://wso2.com/> - Lean . Enterprise . Middleware >>> >>> mobile : +94772891266 >>> >>> >>> >> >> >> -- >> Dinusha Dilrukshi >> Associate Technical Lead >> WSO2 Inc.: http://wso2.com/ >> Mobile: +94725255071 >> Blog: http://dinushasblog.blogspot.com/ >> > > > > -- > > *Ruwan Abeykoon* > *Associate Director/Architect**,* > *WSO2, Inc. http://wso2.com <http://wso2.com/> * > *lean.enterprise.middleware.* > > email: [email protected] > -- Sajith Janaprasad Ariyarathna Software Engineer; WSO2, Inc.; http://wso2.com/
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
