Hi, All of the above points have been addressed and completed. For point 3) we have used the config.json file instead of emm-config.xml file since it holds the configurations of EMM Jaggery app. All the points we have discussed will be available in EMM 1.1.0 release.
Regards, Dilshan On Tue, Jun 3, 2014 at 12:02 AM, Dilshan Edirisuriya <[email protected]> wrote: > Sorry mistakenly sent the mail. > > > > Had a discussion with Sumedha on this. These are the points. > > 1) We will proceed with dynamic consumer key/secret retrieval upon first > time signin to the agent app. It will be stored in the app sandbox securely. > > 2) Auto publish/subscribe and key/secret generation of APIs at super > tenant space will be done at first time login. > > 3) Inorder to login to API manager using REST API we have to keep the > super admin credentials. It will be stored in mdm-config.xml file. > > 4) Issue regarding tenant users not been able to login will be debugged by > the API manager team. > > > Regards, > > Dilshan > > > On Mon, Jun 2, 2014 at 11:57 PM, Dilshan Edirisuriya <[email protected]> > wrote: > >> Hi, >> >> Had a discussion with Sumedha on this. These are the points. >> >> 1) We will proceed with dynamic consumer key/secret retrieval upon first >> time signin to the agent app. It will be stored in the app sandbox securely. >> >> 2) >> >> >> On Mon, Jun 2, 2014 at 1:32 PM, Gayan Gunawardana <[email protected]> wrote: >> >>> >>> >>> >>> On Mon, Jun 2, 2014 at 11:23 AM, Dilshan Edirisuriya <[email protected]> >>> wrote: >>> >>>> Hi Gayan, >>>> >>>> See my comments below. >>>> >>>> "The same requirement in the G-reg also what they have done is use >>>> startup publisher rather using REST APIs. Currently this feature is >>>> available for super tenants only. By extending startup publisher we can >>>> make it available for all tenants. " >>>> >>>> Yes but startup publisher didn't have the facility to publish it for >>>> all tenants. I think its only matter of changing 1 line. The main thing is >>>> there is no startup subscriber. So using Java component to publish and use >>>> REST API to subscribe are 2 different approaches. We wanted to make it >>>> unique on the way we use API manger. That's why we wanted to go ahead with >>>> the REST >>>> >>> >>> mean time there is a another deviation G-reg use startup publisher and >>> EMM use REST APIs so going forward extending start up publisher may be >>> effective for both products since REST API approach has some issues like >>> puting username, password in config files. >>> >>>> >>>> " We can skip these issues if we don't select REST API way. " >>>> >>>> Yes we can skip this if we use the component. But there is no component >>>> for subscription yet. >>>> >>> >>> Ideally we cannot take full advantage of auto subscriber option because >>> getting client id, client secret from particular end point is not available >>> with existing grant types. If we are doing so that will introduce >>> non-standard way of doing things. If we want this feature to just sake of >>> saving first user experience, we can dump default values to databases and >>> put same values in android agent. In production any way we have to compile >>> and build android agent. >>> >>> >> >> >> -- >> Dilshan Edirisuriya >> Senior Software Engineer - WSO2 >> Mob: + 94 777878905 >> http://wso2.com/ >> > > > > -- > Dilshan Edirisuriya > Senior Software Engineer - WSO2 > Mob: + 94 777878905 > http://wso2.com/ > -- Dilshan Edirisuriya Senior Software Engineer - WSO2 Mob: + 94 777878905 http://wso2.com/
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
