I don't see why the App Owner is the person to generate the keys anyway. Normally it would be one of the devs.
This looks like something where we need to define exactly what behaviour we would like to see is, and then implement that in APIM. For example, if I generate keys for an app, who else in the team should see them? I actually don't know the answer to that question. I think we need to figure that out first. Paul On 23 September 2013 10:44, Punnadi Gunarathna <[email protected]> wrote: > > Hi All, > > Myself and Dimuthu had a offline chat regarding $subject and please find > more details on why that cannot be done. > > -If we allow to have multiple App Owners per application then there will > be an issue with APIM. That is; > > "AppOwner1" creates an Application called "App1" in App Factory. Then he > invites > few more people as App Owners say AppOwner2 and AppOwner3. > AppOwner1 login to API Manger and subscribe App1 with "API1" and generate > key pairs. > > Based on the current APIM implementation, any other App Owner who will > login to APIM will not be able to see the previous subscriptions or already > generated keys. Furthermore they can subscribe the same application > individually again with the API1 and generate new keys. > > This is why we thought of not having multiple App Owners per application. > > So then comes the question if the AppOwner1 leaves the company, then how > can we manage the App1 as well as its subscribed APIs? > > In such a situation we thought to provide scripts to update both App > Factory and APIM databases in such a way that the old App Owner will be > updated with the new App Owner details. > > Please let us know your thought on this. > > -- > Thanks and Regards, > > Punnadi Gunarathna > Senior Software Engineer, > WSO2, Inc.; http://wso2.com <http://wso2> > Blog: http://hi-my-world.blogspot.com/ > Tel : 94 11 214 5345 > Fax :94 11 2145300 > > > > <http://lalajisureshika.blogspot.com/> > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, Apache Member UK: +44 207 096 0336 US: +1 646 595 7614 blog: http://pzf.fremantle.org twitter.com/pzfreo [email protected] wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions.
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
