1) IMO the client id and secret here is not something related to the device. For device registration/enrollments we create separate pair from DCR. Hence are we talking about acquiring a pair for webapp/jaggeryapp?
Here as I explained what we need is after enabling SSO in IoTS and DS, on DS side need to invoke REST API which is deployed in IoTs. So this is not regarding device enrollment or registration. 2) If it is for web app there is a possibility that it can be initiated at the DS end. If so since the DCR components are only available in IOTS end how to acquire client id/secret from that end? If we know DCR endpoint on DS side we can create an application and generate client id and secret against created application. On Tue, Apr 26, 2016 at 10:12 AM, Dilshan Edirisuriya <[email protected]> wrote: > Hi Geesara, > > Have couple of questions. > > 1) IMO the client id and secret here is not something related to the > device. For device registration/enrollments we create separate pair from > DCR. Hence are we talking about acquiring a pair for webapp/jaggeryapp? > 2) If it is for web app there is a possibility that it can be initiated at > the DS end. If so since the DCR components are only available in IOT server > end how to acquire client id/secret from that end? > > Regards, > > Dilshan > > On 25 April 2016 at 23:23, Geesara Prathap <[email protected]> wrote: > >> Hi All, >> >> *Use Case:* >> >> User login to IoTS and try to view one of his device types analytics. >> Then the user is redirected to device type analytics page which is in >> dashboard server(DS). Afterwards to retrieve data, gadget needs to invoke a >> REST API which is deployed in IoTS. >> >> In order to intercommunicate between IoTS and DS, SSO should be enabled >> in both applications. To exchange SAML2 bearer token with an OAuth2 access >> token, need to create an application and generate client Id and client >> secret against created application. >> >> To generate client Id and client secret which approach should be used? >> >> 1. Dynamic Client Registration(DCR) approach >> >> 2. OAuthAdminService approach >> >> 3. Other approaches >> >> Thanks, >> >> Geesara >> >> >> -- >> Geesara Prathap Kulathunga >> Software Engineer >> WSO2 Inc; http://wso2.com >> Mobile : +940772684174 >> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Geesara Prathap Kulathunga Software Engineer WSO2 Inc; http://wso2.com Mobile : +940772684174
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
