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,
On Mon, Jun 2, 2014 at 11:23 AM, Dilshan Edirisuriya dils...@wso2.com
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
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 ga...@wso2.com 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
On Sat, May 31, 2014 at 1:00 AM, Dilshan Edirisuriya dils...@wso2.com
wrote:
I am also -1 to that but not sure whether there is a solution if the point
1) is not fulfilling with the use of API manger APIs. Have to check this
with API manager team. I just have proposed a work around by looking
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
Hi,
This is related to the API manager integration with EMM. To describe more
on the usecase we are trying to protect some of the EMM APIs (for now only
Android) using API manager. For this we have included the API manager
features to EMM pack along with the publisher and API store Jaggery apps.
I am also -1 to that but not sure whether there is a solution if the point
1) is not fulfilling with the use of API manger APIs. Have to check this
with API manager team. I just have proposed a work around by looking at
AppFactory.
On Sat, May 31, 2014 at 12:52 AM, Chan duli...@wso2.com wrote:
