Re: [Architecture] [App Factory] Jira Integration for WSO2 App Factory
Hi, I have been successful in getting Issue Summaries from JIRA and displaying it on App Factory. For now, user can specify the url of his jira instance and name of the project from which to retrieve issues. With those information, App Factory accesses user's JIRA instance via OAuth and gets summaries. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Mon, Apr 6, 2015 at 9:04 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, Yeah. I'll work on that. Thanks. Regars, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Mon, Apr 6, 2015 at 9:02 PM, Dimuthu Leelarathne dimut...@wso2.com wrote: Hi, According to our offline discussion we'll do OAuth without managing identities for this implementation. Basically as a user in the app I get redirected JIRA and there I enter credentials to get a summary view, which I believe is good enough for now. thanks, dimuthu On Mon, Apr 6, 2015 at 8:27 PM, Dimuthu Leelarathne dimut...@wso2.com wrote: Hi Dilhasha, How do the authentication happen between JIRA and AF? After configuring once do I have to configure always? thanks, dimuthu On Mon, Apr 6, 2015 at 6:03 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, Please find the mockups at [1] https://docs.google.com/document/d/1SO-K5ryXyfGs2HKBu_0IefNpx4L8ygIU1MfJsJP7-aM/edit?usp=sharing . Please comment and point out any mistakes and improvements. [1] https://docs.google.com/document/d/1SO-K5ryXyfGs2HKBu_0IefNpx4L8ygIU1MfJsJP7-aM/edit?usp=sharing Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Mon, Apr 6, 2015 at 4:43 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Dimuthu, Thank u for pointing out. I think I have made the requirement complex. I will do a mock up and update for this scenario. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Mon, Apr 6, 2015 at 4:05 PM, Dimuthu Leelarathne dimut...@wso2.com wrote: Hi all, We need per app configurations for JIRA. The tasks are pretty simple IMO. 1 - Get the summary from JIRA 2 - Allow user to configure existing JIRA project thanks, dimuthu On Mon, Apr 6, 2015 at 12:22 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Manjula, Thank u for your feedback. If we are going to use a single instance,from the 3 options you've pointed out, I am giving +1 for the third option (Append the tenant domain to the project name). IMO, *1. If the project name is already taken, let user to come up with another project name.* is not an option given the current context. Because as of now, we don't allow user to give a name to a project, we take the project name in JIRA to be similar to the Application name in App Factory. *2. Treating applications as project components* in this scenario (Scenario 3) results in heterogeneity among the scenarios. For example, if user already has a JIRA project we are letting him to use it (as in scenario 1). I am not familiar with starting up a new Jira Catridge per tenant. It would be great if we can do that other than going for a single instance. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Mon, Apr 6, 2015 at 9:15 AM, Manjula Rathnayake manju...@wso2.com wrote: Hi Fathima, Regarding project names, I can see below options based on your document. 1. If the project name is already taken, let user to come up with another project name. 2. Treat applications as jira project components. 3. Append the tenant domain to the project name. If we need to multi tenant the jira, as mentioned in option 3 in document, we can start up new jira cartridge per tenant. If jira instance is provided, and it needs to store multiple tenant projects, we need to choose from above options. thank you. On Fri, Apr 3, 2015 at 10:27 AM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Manjula, Thanks for the feedback. Regarding 1. I agree with you that we can use role based mapping to restrict accessibility to each project. But we will be using the admin user to create apps in the JIRA instance. Given that, I can't still find a way to solve the problem of having similar named projects for two or more tenants. Regarding 2. Are u referring to scenario 3 in the diagram? That is for creating a project in an App Factory defined instance ? If so +1, an admin user can be maintained to do that. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.*
Re: [Architecture] [App Factory] Jira Integration for WSO2 App Factory
Hi Manjula, Thank u for your feedback. If we are going to use a single instance,from the 3 options you've pointed out, I am giving +1 for the third option (Append the tenant domain to the project name). IMO, *1. If the project name is already taken, let user to come up with another project name.* is not an option given the current context. Because as of now, we don't allow user to give a name to a project, we take the project name in JIRA to be similar to the Application name in App Factory. *2. Treating applications as project components* in this scenario (Scenario 3) results in heterogeneity among the scenarios. For example, if user already has a JIRA project we are letting him to use it (as in scenario 1). I am not familiar with starting up a new Jira Catridge per tenant. It would be great if we can do that other than going for a single instance. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Mon, Apr 6, 2015 at 9:15 AM, Manjula Rathnayake manju...@wso2.com wrote: Hi Fathima, Regarding project names, I can see below options based on your document. 1. If the project name is already taken, let user to come up with another project name. 2. Treat applications as jira project components. 3. Append the tenant domain to the project name. If we need to multi tenant the jira, as mentioned in option 3 in document, we can start up new jira cartridge per tenant. If jira instance is provided, and it needs to store multiple tenant projects, we need to choose from above options. thank you. On Fri, Apr 3, 2015 at 10:27 AM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Manjula, Thanks for the feedback. Regarding 1. I agree with you that we can use role based mapping to restrict accessibility to each project. But we will be using the admin user to create apps in the JIRA instance. Given that, I can't still find a way to solve the problem of having similar named projects for two or more tenants. Regarding 2. Are u referring to scenario 3 in the diagram? That is for creating a project in an App Factory defined instance ? If so +1, an admin user can be maintained to do that. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Fri, Apr 3, 2015 at 9:44 AM, Manjula Rathnayake manju...@wso2.com wrote: Hi all, This is regarding using a single JIRA instance for all apps in all tenants. 1. Using the role based access control, we can restrict users seeing other tenant applications. ex: foo tenant users are assigned to foo_role in jira. @Dilhasha, Please have a look at jira role mapping to jira projects. 2. Regarding the login issue, we can use a predefined system user in jira to create projects, assign users on behalf of other users. thank you. On Fri, Apr 3, 2015 at 12:50 AM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, I have specified a flow chart and my suggestions regarding the scenarios in [1]. https://docs.google.com/document/d/1qDRObBh4CLnO755TgyINWAey9c1X3W1BFI-hgkh9rlQ/edit?usp=sharing Please comment and point out any mistakes and suggest any other options we can consider. [1] https://docs.google.com/document/d/1qDRObBh4CLnO755TgyINWAey9c1X3W1BFI-hgkh9rlQ/edit?usp=sharing Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 10:38 PM, Anuruddha Premalal anurud...@wso2.com wrote: Hi Punnadi, We cannot store credentials in a configuration file since this is a per application configuration. Regards, Anuruddha. On Wed, Apr 1, 2015 at 9:43 AM, Punnadi Gunarathna punn...@wso2.com wrote: Hi Fathima, Can't we store the credentials in a configuration file, which are required to create the JIRA instance? If that is possible, We can make use of Secure Vault to secure the plain text password. WDYT? On Apr 1, 2015 8:04 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, Okay, now I understand your first question. AFAIK, there is no way to customize authentication behavior, in a way that we can allow to have similar project names for different tenants. We can have groups of users and manage visibility of each project on a single JIRA instance, among users in that instance as specified in [1] https://confluence.atlassian.com/display/Cloud/Managing+project+visibility . What you are suggesting is to map a user in JIRA to a particular tenant in App Factory, is it? [1] https://confluence.atlassian.com/display/Cloud/Managing+project+visibility Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 7:56 PM, danush...@wso2.com
Re: [Architecture] [App Factory] Jira Integration for WSO2 App Factory
Hi all, We need per app configurations for JIRA. The tasks are pretty simple IMO. 1 - Get the summary from JIRA 2 - Allow user to configure existing JIRA project thanks, dimuthu On Mon, Apr 6, 2015 at 12:22 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Manjula, Thank u for your feedback. If we are going to use a single instance,from the 3 options you've pointed out, I am giving +1 for the third option (Append the tenant domain to the project name). IMO, *1. If the project name is already taken, let user to come up with another project name.* is not an option given the current context. Because as of now, we don't allow user to give a name to a project, we take the project name in JIRA to be similar to the Application name in App Factory. *2. Treating applications as project components* in this scenario (Scenario 3) results in heterogeneity among the scenarios. For example, if user already has a JIRA project we are letting him to use it (as in scenario 1). I am not familiar with starting up a new Jira Catridge per tenant. It would be great if we can do that other than going for a single instance. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Mon, Apr 6, 2015 at 9:15 AM, Manjula Rathnayake manju...@wso2.com wrote: Hi Fathima, Regarding project names, I can see below options based on your document. 1. If the project name is already taken, let user to come up with another project name. 2. Treat applications as jira project components. 3. Append the tenant domain to the project name. If we need to multi tenant the jira, as mentioned in option 3 in document, we can start up new jira cartridge per tenant. If jira instance is provided, and it needs to store multiple tenant projects, we need to choose from above options. thank you. On Fri, Apr 3, 2015 at 10:27 AM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Manjula, Thanks for the feedback. Regarding 1. I agree with you that we can use role based mapping to restrict accessibility to each project. But we will be using the admin user to create apps in the JIRA instance. Given that, I can't still find a way to solve the problem of having similar named projects for two or more tenants. Regarding 2. Are u referring to scenario 3 in the diagram? That is for creating a project in an App Factory defined instance ? If so +1, an admin user can be maintained to do that. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Fri, Apr 3, 2015 at 9:44 AM, Manjula Rathnayake manju...@wso2.com wrote: Hi all, This is regarding using a single JIRA instance for all apps in all tenants. 1. Using the role based access control, we can restrict users seeing other tenant applications. ex: foo tenant users are assigned to foo_role in jira. @Dilhasha, Please have a look at jira role mapping to jira projects. 2. Regarding the login issue, we can use a predefined system user in jira to create projects, assign users on behalf of other users. thank you. On Fri, Apr 3, 2015 at 12:50 AM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, I have specified a flow chart and my suggestions regarding the scenarios in [1]. https://docs.google.com/document/d/1qDRObBh4CLnO755TgyINWAey9c1X3W1BFI-hgkh9rlQ/edit?usp=sharing Please comment and point out any mistakes and suggest any other options we can consider. [1] https://docs.google.com/document/d/1qDRObBh4CLnO755TgyINWAey9c1X3W1BFI-hgkh9rlQ/edit?usp=sharing Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 10:38 PM, Anuruddha Premalal anurud...@wso2.com wrote: Hi Punnadi, We cannot store credentials in a configuration file since this is a per application configuration. Regards, Anuruddha. On Wed, Apr 1, 2015 at 9:43 AM, Punnadi Gunarathna punn...@wso2.com wrote: Hi Fathima, Can't we store the credentials in a configuration file, which are required to create the JIRA instance? If that is possible, We can make use of Secure Vault to secure the plain text password. WDYT? On Apr 1, 2015 8:04 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, Okay, now I understand your first question. AFAIK, there is no way to customize authentication behavior, in a way that we can allow to have similar project names for different tenants. We can have groups of users and manage visibility of each project on a single JIRA instance, among users in that instance as specified in [1] https://confluence.atlassian.com/display/Cloud/Managing+project+visibility . What you are suggesting is to map a user in JIRA to a particular tenant in App Factory, is it? [1]
Re: [Architecture] [App Factory] Jira Integration for WSO2 App Factory
Hi Dimuthu, Thank u for pointing out. I think I have made the requirement complex. I will do a mock up and update for this scenario. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Mon, Apr 6, 2015 at 4:05 PM, Dimuthu Leelarathne dimut...@wso2.com wrote: Hi all, We need per app configurations for JIRA. The tasks are pretty simple IMO. 1 - Get the summary from JIRA 2 - Allow user to configure existing JIRA project thanks, dimuthu On Mon, Apr 6, 2015 at 12:22 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Manjula, Thank u for your feedback. If we are going to use a single instance,from the 3 options you've pointed out, I am giving +1 for the third option (Append the tenant domain to the project name). IMO, *1. If the project name is already taken, let user to come up with another project name.* is not an option given the current context. Because as of now, we don't allow user to give a name to a project, we take the project name in JIRA to be similar to the Application name in App Factory. *2. Treating applications as project components* in this scenario (Scenario 3) results in heterogeneity among the scenarios. For example, if user already has a JIRA project we are letting him to use it (as in scenario 1). I am not familiar with starting up a new Jira Catridge per tenant. It would be great if we can do that other than going for a single instance. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Mon, Apr 6, 2015 at 9:15 AM, Manjula Rathnayake manju...@wso2.com wrote: Hi Fathima, Regarding project names, I can see below options based on your document. 1. If the project name is already taken, let user to come up with another project name. 2. Treat applications as jira project components. 3. Append the tenant domain to the project name. If we need to multi tenant the jira, as mentioned in option 3 in document, we can start up new jira cartridge per tenant. If jira instance is provided, and it needs to store multiple tenant projects, we need to choose from above options. thank you. On Fri, Apr 3, 2015 at 10:27 AM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Manjula, Thanks for the feedback. Regarding 1. I agree with you that we can use role based mapping to restrict accessibility to each project. But we will be using the admin user to create apps in the JIRA instance. Given that, I can't still find a way to solve the problem of having similar named projects for two or more tenants. Regarding 2. Are u referring to scenario 3 in the diagram? That is for creating a project in an App Factory defined instance ? If so +1, an admin user can be maintained to do that. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Fri, Apr 3, 2015 at 9:44 AM, Manjula Rathnayake manju...@wso2.com wrote: Hi all, This is regarding using a single JIRA instance for all apps in all tenants. 1. Using the role based access control, we can restrict users seeing other tenant applications. ex: foo tenant users are assigned to foo_role in jira. @Dilhasha, Please have a look at jira role mapping to jira projects. 2. Regarding the login issue, we can use a predefined system user in jira to create projects, assign users on behalf of other users. thank you. On Fri, Apr 3, 2015 at 12:50 AM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, I have specified a flow chart and my suggestions regarding the scenarios in [1]. https://docs.google.com/document/d/1qDRObBh4CLnO755TgyINWAey9c1X3W1BFI-hgkh9rlQ/edit?usp=sharing Please comment and point out any mistakes and suggest any other options we can consider. [1] https://docs.google.com/document/d/1qDRObBh4CLnO755TgyINWAey9c1X3W1BFI-hgkh9rlQ/edit?usp=sharing Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 10:38 PM, Anuruddha Premalal anurud...@wso2.com wrote: Hi Punnadi, We cannot store credentials in a configuration file since this is a per application configuration. Regards, Anuruddha. On Wed, Apr 1, 2015 at 9:43 AM, Punnadi Gunarathna punn...@wso2.com wrote: Hi Fathima, Can't we store the credentials in a configuration file, which are required to create the JIRA instance? If that is possible, We can make use of Secure Vault to secure the plain text password. WDYT? On Apr 1, 2015 8:04 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, Okay, now I understand your first question. AFAIK, there is no way to customize authentication behavior, in a way that we can allow to have
Re: [Architecture] [App Factory] Jira Integration for WSO2 App Factory
Hi, Please find the mockups at [1] https://docs.google.com/document/d/1SO-K5ryXyfGs2HKBu_0IefNpx4L8ygIU1MfJsJP7-aM/edit?usp=sharing . Please comment and point out any mistakes and improvements. [1] https://docs.google.com/document/d/1SO-K5ryXyfGs2HKBu_0IefNpx4L8ygIU1MfJsJP7-aM/edit?usp=sharing Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Mon, Apr 6, 2015 at 4:43 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Dimuthu, Thank u for pointing out. I think I have made the requirement complex. I will do a mock up and update for this scenario. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Mon, Apr 6, 2015 at 4:05 PM, Dimuthu Leelarathne dimut...@wso2.com wrote: Hi all, We need per app configurations for JIRA. The tasks are pretty simple IMO. 1 - Get the summary from JIRA 2 - Allow user to configure existing JIRA project thanks, dimuthu On Mon, Apr 6, 2015 at 12:22 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Manjula, Thank u for your feedback. If we are going to use a single instance,from the 3 options you've pointed out, I am giving +1 for the third option (Append the tenant domain to the project name). IMO, *1. If the project name is already taken, let user to come up with another project name.* is not an option given the current context. Because as of now, we don't allow user to give a name to a project, we take the project name in JIRA to be similar to the Application name in App Factory. *2. Treating applications as project components* in this scenario (Scenario 3) results in heterogeneity among the scenarios. For example, if user already has a JIRA project we are letting him to use it (as in scenario 1). I am not familiar with starting up a new Jira Catridge per tenant. It would be great if we can do that other than going for a single instance. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Mon, Apr 6, 2015 at 9:15 AM, Manjula Rathnayake manju...@wso2.com wrote: Hi Fathima, Regarding project names, I can see below options based on your document. 1. If the project name is already taken, let user to come up with another project name. 2. Treat applications as jira project components. 3. Append the tenant domain to the project name. If we need to multi tenant the jira, as mentioned in option 3 in document, we can start up new jira cartridge per tenant. If jira instance is provided, and it needs to store multiple tenant projects, we need to choose from above options. thank you. On Fri, Apr 3, 2015 at 10:27 AM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Manjula, Thanks for the feedback. Regarding 1. I agree with you that we can use role based mapping to restrict accessibility to each project. But we will be using the admin user to create apps in the JIRA instance. Given that, I can't still find a way to solve the problem of having similar named projects for two or more tenants. Regarding 2. Are u referring to scenario 3 in the diagram? That is for creating a project in an App Factory defined instance ? If so +1, an admin user can be maintained to do that. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Fri, Apr 3, 2015 at 9:44 AM, Manjula Rathnayake manju...@wso2.com wrote: Hi all, This is regarding using a single JIRA instance for all apps in all tenants. 1. Using the role based access control, we can restrict users seeing other tenant applications. ex: foo tenant users are assigned to foo_role in jira. @Dilhasha, Please have a look at jira role mapping to jira projects. 2. Regarding the login issue, we can use a predefined system user in jira to create projects, assign users on behalf of other users. thank you. On Fri, Apr 3, 2015 at 12:50 AM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, I have specified a flow chart and my suggestions regarding the scenarios in [1]. https://docs.google.com/document/d/1qDRObBh4CLnO755TgyINWAey9c1X3W1BFI-hgkh9rlQ/edit?usp=sharing Please comment and point out any mistakes and suggest any other options we can consider. [1] https://docs.google.com/document/d/1qDRObBh4CLnO755TgyINWAey9c1X3W1BFI-hgkh9rlQ/edit?usp=sharing Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 10:38 PM, Anuruddha Premalal anurud...@wso2.com wrote: Hi Punnadi, We cannot store credentials in a configuration file since this is a per application
Re: [Architecture] [App Factory] Jira Integration for WSO2 App Factory
Hi Dilhasha, How do the authentication happen between JIRA and AF? After configuring once do I have to configure always? thanks, dimuthu On Mon, Apr 6, 2015 at 6:03 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, Please find the mockups at [1] https://docs.google.com/document/d/1SO-K5ryXyfGs2HKBu_0IefNpx4L8ygIU1MfJsJP7-aM/edit?usp=sharing . Please comment and point out any mistakes and improvements. [1] https://docs.google.com/document/d/1SO-K5ryXyfGs2HKBu_0IefNpx4L8ygIU1MfJsJP7-aM/edit?usp=sharing Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Mon, Apr 6, 2015 at 4:43 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Dimuthu, Thank u for pointing out. I think I have made the requirement complex. I will do a mock up and update for this scenario. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Mon, Apr 6, 2015 at 4:05 PM, Dimuthu Leelarathne dimut...@wso2.com wrote: Hi all, We need per app configurations for JIRA. The tasks are pretty simple IMO. 1 - Get the summary from JIRA 2 - Allow user to configure existing JIRA project thanks, dimuthu On Mon, Apr 6, 2015 at 12:22 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Manjula, Thank u for your feedback. If we are going to use a single instance,from the 3 options you've pointed out, I am giving +1 for the third option (Append the tenant domain to the project name). IMO, *1. If the project name is already taken, let user to come up with another project name.* is not an option given the current context. Because as of now, we don't allow user to give a name to a project, we take the project name in JIRA to be similar to the Application name in App Factory. *2. Treating applications as project components* in this scenario (Scenario 3) results in heterogeneity among the scenarios. For example, if user already has a JIRA project we are letting him to use it (as in scenario 1). I am not familiar with starting up a new Jira Catridge per tenant. It would be great if we can do that other than going for a single instance. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Mon, Apr 6, 2015 at 9:15 AM, Manjula Rathnayake manju...@wso2.com wrote: Hi Fathima, Regarding project names, I can see below options based on your document. 1. If the project name is already taken, let user to come up with another project name. 2. Treat applications as jira project components. 3. Append the tenant domain to the project name. If we need to multi tenant the jira, as mentioned in option 3 in document, we can start up new jira cartridge per tenant. If jira instance is provided, and it needs to store multiple tenant projects, we need to choose from above options. thank you. On Fri, Apr 3, 2015 at 10:27 AM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Manjula, Thanks for the feedback. Regarding 1. I agree with you that we can use role based mapping to restrict accessibility to each project. But we will be using the admin user to create apps in the JIRA instance. Given that, I can't still find a way to solve the problem of having similar named projects for two or more tenants. Regarding 2. Are u referring to scenario 3 in the diagram? That is for creating a project in an App Factory defined instance ? If so +1, an admin user can be maintained to do that. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Fri, Apr 3, 2015 at 9:44 AM, Manjula Rathnayake manju...@wso2.com wrote: Hi all, This is regarding using a single JIRA instance for all apps in all tenants. 1. Using the role based access control, we can restrict users seeing other tenant applications. ex: foo tenant users are assigned to foo_role in jira. @Dilhasha, Please have a look at jira role mapping to jira projects. 2. Regarding the login issue, we can use a predefined system user in jira to create projects, assign users on behalf of other users. thank you. On Fri, Apr 3, 2015 at 12:50 AM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, I have specified a flow chart and my suggestions regarding the scenarios in [1]. https://docs.google.com/document/d/1qDRObBh4CLnO755TgyINWAey9c1X3W1BFI-hgkh9rlQ/edit?usp=sharing Please comment and point out any mistakes and suggest any other options we can consider. [1] https://docs.google.com/document/d/1qDRObBh4CLnO755TgyINWAey9c1X3W1BFI-hgkh9rlQ/edit?usp=sharing Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email :
Re: [Architecture] [App Factory] Jira Integration for WSO2 App Factory
Hi, Yeah. I'll work on that. Thanks. Regars, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Mon, Apr 6, 2015 at 9:02 PM, Dimuthu Leelarathne dimut...@wso2.com wrote: Hi, According to our offline discussion we'll do OAuth without managing identities for this implementation. Basically as a user in the app I get redirected JIRA and there I enter credentials to get a summary view, which I believe is good enough for now. thanks, dimuthu On Mon, Apr 6, 2015 at 8:27 PM, Dimuthu Leelarathne dimut...@wso2.com wrote: Hi Dilhasha, How do the authentication happen between JIRA and AF? After configuring once do I have to configure always? thanks, dimuthu On Mon, Apr 6, 2015 at 6:03 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, Please find the mockups at [1] https://docs.google.com/document/d/1SO-K5ryXyfGs2HKBu_0IefNpx4L8ygIU1MfJsJP7-aM/edit?usp=sharing . Please comment and point out any mistakes and improvements. [1] https://docs.google.com/document/d/1SO-K5ryXyfGs2HKBu_0IefNpx4L8ygIU1MfJsJP7-aM/edit?usp=sharing Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Mon, Apr 6, 2015 at 4:43 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Dimuthu, Thank u for pointing out. I think I have made the requirement complex. I will do a mock up and update for this scenario. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Mon, Apr 6, 2015 at 4:05 PM, Dimuthu Leelarathne dimut...@wso2.com wrote: Hi all, We need per app configurations for JIRA. The tasks are pretty simple IMO. 1 - Get the summary from JIRA 2 - Allow user to configure existing JIRA project thanks, dimuthu On Mon, Apr 6, 2015 at 12:22 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Manjula, Thank u for your feedback. If we are going to use a single instance,from the 3 options you've pointed out, I am giving +1 for the third option (Append the tenant domain to the project name). IMO, *1. If the project name is already taken, let user to come up with another project name.* is not an option given the current context. Because as of now, we don't allow user to give a name to a project, we take the project name in JIRA to be similar to the Application name in App Factory. *2. Treating applications as project components* in this scenario (Scenario 3) results in heterogeneity among the scenarios. For example, if user already has a JIRA project we are letting him to use it (as in scenario 1). I am not familiar with starting up a new Jira Catridge per tenant. It would be great if we can do that other than going for a single instance. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Mon, Apr 6, 2015 at 9:15 AM, Manjula Rathnayake manju...@wso2.com wrote: Hi Fathima, Regarding project names, I can see below options based on your document. 1. If the project name is already taken, let user to come up with another project name. 2. Treat applications as jira project components. 3. Append the tenant domain to the project name. If we need to multi tenant the jira, as mentioned in option 3 in document, we can start up new jira cartridge per tenant. If jira instance is provided, and it needs to store multiple tenant projects, we need to choose from above options. thank you. On Fri, Apr 3, 2015 at 10:27 AM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Manjula, Thanks for the feedback. Regarding 1. I agree with you that we can use role based mapping to restrict accessibility to each project. But we will be using the admin user to create apps in the JIRA instance. Given that, I can't still find a way to solve the problem of having similar named projects for two or more tenants. Regarding 2. Are u referring to scenario 3 in the diagram? That is for creating a project in an App Factory defined instance ? If so +1, an admin user can be maintained to do that. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Fri, Apr 3, 2015 at 9:44 AM, Manjula Rathnayake manju...@wso2.com wrote: Hi all, This is regarding using a single JIRA instance for all apps in all tenants. 1. Using the role based access control, we can restrict users seeing other tenant applications. ex: foo tenant users are assigned to foo_role in jira. @Dilhasha, Please have a look at jira role mapping to jira projects. 2. Regarding the login issue, we can use a predefined system user in jira to create
Re: [Architecture] [App Factory] Jira Integration for WSO2 App Factory
Hi, According to our offline discussion we'll do OAuth without managing identities for this implementation. Basically as a user in the app I get redirected JIRA and there I enter credentials to get a summary view, which I believe is good enough for now. thanks, dimuthu On Mon, Apr 6, 2015 at 8:27 PM, Dimuthu Leelarathne dimut...@wso2.com wrote: Hi Dilhasha, How do the authentication happen between JIRA and AF? After configuring once do I have to configure always? thanks, dimuthu On Mon, Apr 6, 2015 at 6:03 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, Please find the mockups at [1] https://docs.google.com/document/d/1SO-K5ryXyfGs2HKBu_0IefNpx4L8ygIU1MfJsJP7-aM/edit?usp=sharing . Please comment and point out any mistakes and improvements. [1] https://docs.google.com/document/d/1SO-K5ryXyfGs2HKBu_0IefNpx4L8ygIU1MfJsJP7-aM/edit?usp=sharing Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Mon, Apr 6, 2015 at 4:43 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Dimuthu, Thank u for pointing out. I think I have made the requirement complex. I will do a mock up and update for this scenario. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Mon, Apr 6, 2015 at 4:05 PM, Dimuthu Leelarathne dimut...@wso2.com wrote: Hi all, We need per app configurations for JIRA. The tasks are pretty simple IMO. 1 - Get the summary from JIRA 2 - Allow user to configure existing JIRA project thanks, dimuthu On Mon, Apr 6, 2015 at 12:22 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Manjula, Thank u for your feedback. If we are going to use a single instance,from the 3 options you've pointed out, I am giving +1 for the third option (Append the tenant domain to the project name). IMO, *1. If the project name is already taken, let user to come up with another project name.* is not an option given the current context. Because as of now, we don't allow user to give a name to a project, we take the project name in JIRA to be similar to the Application name in App Factory. *2. Treating applications as project components* in this scenario (Scenario 3) results in heterogeneity among the scenarios. For example, if user already has a JIRA project we are letting him to use it (as in scenario 1). I am not familiar with starting up a new Jira Catridge per tenant. It would be great if we can do that other than going for a single instance. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Mon, Apr 6, 2015 at 9:15 AM, Manjula Rathnayake manju...@wso2.com wrote: Hi Fathima, Regarding project names, I can see below options based on your document. 1. If the project name is already taken, let user to come up with another project name. 2. Treat applications as jira project components. 3. Append the tenant domain to the project name. If we need to multi tenant the jira, as mentioned in option 3 in document, we can start up new jira cartridge per tenant. If jira instance is provided, and it needs to store multiple tenant projects, we need to choose from above options. thank you. On Fri, Apr 3, 2015 at 10:27 AM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Manjula, Thanks for the feedback. Regarding 1. I agree with you that we can use role based mapping to restrict accessibility to each project. But we will be using the admin user to create apps in the JIRA instance. Given that, I can't still find a way to solve the problem of having similar named projects for two or more tenants. Regarding 2. Are u referring to scenario 3 in the diagram? That is for creating a project in an App Factory defined instance ? If so +1, an admin user can be maintained to do that. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Fri, Apr 3, 2015 at 9:44 AM, Manjula Rathnayake manju...@wso2.com wrote: Hi all, This is regarding using a single JIRA instance for all apps in all tenants. 1. Using the role based access control, we can restrict users seeing other tenant applications. ex: foo tenant users are assigned to foo_role in jira. @Dilhasha, Please have a look at jira role mapping to jira projects. 2. Regarding the login issue, we can use a predefined system user in jira to create projects, assign users on behalf of other users. thank you. On Fri, Apr 3, 2015 at 12:50 AM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, I have specified a flow chart and my suggestions regarding the scenarios in [1].
Re: [Architecture] [App Factory] Jira Integration for WSO2 App Factory
Hi Fathima, Regarding project names, I can see below options based on your document. 1. If the project name is already taken, let user to come up with another project name. 2. Treat applications as jira project components. 3. Append the tenant domain to the project name. If we need to multi tenant the jira, as mentioned in option 3 in document, we can start up new jira cartridge per tenant. If jira instance is provided, and it needs to store multiple tenant projects, we need to choose from above options. thank you. On Fri, Apr 3, 2015 at 10:27 AM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Manjula, Thanks for the feedback. Regarding 1. I agree with you that we can use role based mapping to restrict accessibility to each project. But we will be using the admin user to create apps in the JIRA instance. Given that, I can't still find a way to solve the problem of having similar named projects for two or more tenants. Regarding 2. Are u referring to scenario 3 in the diagram? That is for creating a project in an App Factory defined instance ? If so +1, an admin user can be maintained to do that. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Fri, Apr 3, 2015 at 9:44 AM, Manjula Rathnayake manju...@wso2.com wrote: Hi all, This is regarding using a single JIRA instance for all apps in all tenants. 1. Using the role based access control, we can restrict users seeing other tenant applications. ex: foo tenant users are assigned to foo_role in jira. @Dilhasha, Please have a look at jira role mapping to jira projects. 2. Regarding the login issue, we can use a predefined system user in jira to create projects, assign users on behalf of other users. thank you. On Fri, Apr 3, 2015 at 12:50 AM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, I have specified a flow chart and my suggestions regarding the scenarios in [1]. https://docs.google.com/document/d/1qDRObBh4CLnO755TgyINWAey9c1X3W1BFI-hgkh9rlQ/edit?usp=sharing Please comment and point out any mistakes and suggest any other options we can consider. [1] https://docs.google.com/document/d/1qDRObBh4CLnO755TgyINWAey9c1X3W1BFI-hgkh9rlQ/edit?usp=sharing Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 10:38 PM, Anuruddha Premalal anurud...@wso2.com wrote: Hi Punnadi, We cannot store credentials in a configuration file since this is a per application configuration. Regards, Anuruddha. On Wed, Apr 1, 2015 at 9:43 AM, Punnadi Gunarathna punn...@wso2.com wrote: Hi Fathima, Can't we store the credentials in a configuration file, which are required to create the JIRA instance? If that is possible, We can make use of Secure Vault to secure the plain text password. WDYT? On Apr 1, 2015 8:04 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, Okay, now I understand your first question. AFAIK, there is no way to customize authentication behavior, in a way that we can allow to have similar project names for different tenants. We can have groups of users and manage visibility of each project on a single JIRA instance, among users in that instance as specified in [1] https://confluence.atlassian.com/display/Cloud/Managing+project+visibility . What you are suggesting is to map a user in JIRA to a particular tenant in App Factory, is it? [1] https://confluence.atlassian.com/display/Cloud/Managing+project+visibility Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 7:56 PM, danush...@wso2.com wrote: /s/pretty/pre Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 *From:* Danushka Fernando danush...@wso2.com *Sent:* Wednesday, April 1, 2015 7:30 PM *To:* architecture architecture@wso2.org I understand that fact. What I was asking is can we customize the authentication behavior. Are there extension points. Any way if there are not you can have a pretty defined user for each tenant same as we do for jenkins. Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 On Apr 1, 2015 7:14 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi danushka, The issue is with how the SOAP API for JIRA works. It requires admin username and password to establish a SOAP session, to create a project via the SOAP API. If we are to create a project on a user specified JIRA instance, the username and password (For that particular JIRA instance) are required. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com
Re: [Architecture] [App Factory] Jira Integration for WSO2 App Factory
Hi all, This is regarding using a single JIRA instance for all apps in all tenants. 1. Using the role based access control, we can restrict users seeing other tenant applications. ex: foo tenant users are assigned to foo_role in jira. @Dilhasha, Please have a look at jira role mapping to jira projects. 2. Regarding the login issue, we can use a predefined system user in jira to create projects, assign users on behalf of other users. thank you. On Fri, Apr 3, 2015 at 12:50 AM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, I have specified a flow chart and my suggestions regarding the scenarios in [1]. https://docs.google.com/document/d/1qDRObBh4CLnO755TgyINWAey9c1X3W1BFI-hgkh9rlQ/edit?usp=sharing Please comment and point out any mistakes and suggest any other options we can consider. [1] https://docs.google.com/document/d/1qDRObBh4CLnO755TgyINWAey9c1X3W1BFI-hgkh9rlQ/edit?usp=sharing Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 10:38 PM, Anuruddha Premalal anurud...@wso2.com wrote: Hi Punnadi, We cannot store credentials in a configuration file since this is a per application configuration. Regards, Anuruddha. On Wed, Apr 1, 2015 at 9:43 AM, Punnadi Gunarathna punn...@wso2.com wrote: Hi Fathima, Can't we store the credentials in a configuration file, which are required to create the JIRA instance? If that is possible, We can make use of Secure Vault to secure the plain text password. WDYT? On Apr 1, 2015 8:04 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, Okay, now I understand your first question. AFAIK, there is no way to customize authentication behavior, in a way that we can allow to have similar project names for different tenants. We can have groups of users and manage visibility of each project on a single JIRA instance, among users in that instance as specified in [1] https://confluence.atlassian.com/display/Cloud/Managing+project+visibility . What you are suggesting is to map a user in JIRA to a particular tenant in App Factory, is it? [1] https://confluence.atlassian.com/display/Cloud/Managing+project+visibility Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 7:56 PM, danush...@wso2.com wrote: /s/pretty/pre Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 *From:* Danushka Fernando danush...@wso2.com *Sent:* Wednesday, April 1, 2015 7:30 PM *To:* architecture architecture@wso2.org I understand that fact. What I was asking is can we customize the authentication behavior. Are there extension points. Any way if there are not you can have a pretty defined user for each tenant same as we do for jenkins. Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 On Apr 1, 2015 7:14 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi danushka, The issue is with how the SOAP API for JIRA works. It requires admin username and password to establish a SOAP session, to create a project via the SOAP API. If we are to create a project on a user specified JIRA instance, the username and password (For that particular JIRA instance) are required. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 6:07 PM, Danushka Fernando danush...@wso2.com wrote: Hi Are there extension points in jira where we can extend authentication mechanism. BTW password is something we don't have. We have only username. Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 On Apr 1, 2015 4:25 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, I need few other clarifications as well. So far, I have been successful in creating a JIRA project via SOAP only. This SOAP client requires username and password for the Jira instance. So, if we want to allow users to create projects in their JIRA instance, we will have to request for username and password for JIRA instance. Is that okay? We will not store any username or password, but we'll need it to create a SOAP session. WDYT? Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 2:34 PM, Fathima Dilhasha dilha...@wso2.com wrote: The prices for cloud and server instances of JIRA are the same as mentioned in [1] https://www.atlassian.com/software/jira/pricing/?tab=cloud. [1]https://www.atlassian.com/software/jira/pricing/?tab=cloud Thanks. *M.N.F. Dilhasha*
Re: [Architecture] [App Factory] Jira Integration for WSO2 App Factory
Hi Manjula, Thanks for the feedback. Regarding 1. I agree with you that we can use role based mapping to restrict accessibility to each project. But we will be using the admin user to create apps in the JIRA instance. Given that, I can't still find a way to solve the problem of having similar named projects for two or more tenants. Regarding 2. Are u referring to scenario 3 in the diagram? That is for creating a project in an App Factory defined instance ? If so +1, an admin user can be maintained to do that. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Fri, Apr 3, 2015 at 9:44 AM, Manjula Rathnayake manju...@wso2.com wrote: Hi all, This is regarding using a single JIRA instance for all apps in all tenants. 1. Using the role based access control, we can restrict users seeing other tenant applications. ex: foo tenant users are assigned to foo_role in jira. @Dilhasha, Please have a look at jira role mapping to jira projects. 2. Regarding the login issue, we can use a predefined system user in jira to create projects, assign users on behalf of other users. thank you. On Fri, Apr 3, 2015 at 12:50 AM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, I have specified a flow chart and my suggestions regarding the scenarios in [1]. https://docs.google.com/document/d/1qDRObBh4CLnO755TgyINWAey9c1X3W1BFI-hgkh9rlQ/edit?usp=sharing Please comment and point out any mistakes and suggest any other options we can consider. [1] https://docs.google.com/document/d/1qDRObBh4CLnO755TgyINWAey9c1X3W1BFI-hgkh9rlQ/edit?usp=sharing Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 10:38 PM, Anuruddha Premalal anurud...@wso2.com wrote: Hi Punnadi, We cannot store credentials in a configuration file since this is a per application configuration. Regards, Anuruddha. On Wed, Apr 1, 2015 at 9:43 AM, Punnadi Gunarathna punn...@wso2.com wrote: Hi Fathima, Can't we store the credentials in a configuration file, which are required to create the JIRA instance? If that is possible, We can make use of Secure Vault to secure the plain text password. WDYT? On Apr 1, 2015 8:04 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, Okay, now I understand your first question. AFAIK, there is no way to customize authentication behavior, in a way that we can allow to have similar project names for different tenants. We can have groups of users and manage visibility of each project on a single JIRA instance, among users in that instance as specified in [1] https://confluence.atlassian.com/display/Cloud/Managing+project+visibility . What you are suggesting is to map a user in JIRA to a particular tenant in App Factory, is it? [1] https://confluence.atlassian.com/display/Cloud/Managing+project+visibility Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 7:56 PM, danush...@wso2.com wrote: /s/pretty/pre Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 *From:* Danushka Fernando danush...@wso2.com *Sent:* Wednesday, April 1, 2015 7:30 PM *To:* architecture architecture@wso2.org I understand that fact. What I was asking is can we customize the authentication behavior. Are there extension points. Any way if there are not you can have a pretty defined user for each tenant same as we do for jenkins. Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 On Apr 1, 2015 7:14 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi danushka, The issue is with how the SOAP API for JIRA works. It requires admin username and password to establish a SOAP session, to create a project via the SOAP API. If we are to create a project on a user specified JIRA instance, the username and password (For that particular JIRA instance) are required. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 6:07 PM, Danushka Fernando danush...@wso2.com wrote: Hi Are there extension points in jira where we can extend authentication mechanism. BTW password is something we don't have. We have only username. Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 On Apr 1, 2015 4:25 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, I need few other clarifications as well. So far, I have been successful in creating a JIRA project via SOAP only. This SOAP client requires username and password for the
Re: [Architecture] [App Factory] Jira Integration for WSO2 App Factory
Hi, I have specified a flow chart and my suggestions regarding the scenarios in [1]. https://docs.google.com/document/d/1qDRObBh4CLnO755TgyINWAey9c1X3W1BFI-hgkh9rlQ/edit?usp=sharing Please comment and point out any mistakes and suggest any other options we can consider. [1] https://docs.google.com/document/d/1qDRObBh4CLnO755TgyINWAey9c1X3W1BFI-hgkh9rlQ/edit?usp=sharing Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 10:38 PM, Anuruddha Premalal anurud...@wso2.com wrote: Hi Punnadi, We cannot store credentials in a configuration file since this is a per application configuration. Regards, Anuruddha. On Wed, Apr 1, 2015 at 9:43 AM, Punnadi Gunarathna punn...@wso2.com wrote: Hi Fathima, Can't we store the credentials in a configuration file, which are required to create the JIRA instance? If that is possible, We can make use of Secure Vault to secure the plain text password. WDYT? On Apr 1, 2015 8:04 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, Okay, now I understand your first question. AFAIK, there is no way to customize authentication behavior, in a way that we can allow to have similar project names for different tenants. We can have groups of users and manage visibility of each project on a single JIRA instance, among users in that instance as specified in [1] https://confluence.atlassian.com/display/Cloud/Managing+project+visibility . What you are suggesting is to map a user in JIRA to a particular tenant in App Factory, is it? [1] https://confluence.atlassian.com/display/Cloud/Managing+project+visibility Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 7:56 PM, danush...@wso2.com wrote: /s/pretty/pre Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 *From:* Danushka Fernando danush...@wso2.com *Sent:* Wednesday, April 1, 2015 7:30 PM *To:* architecture architecture@wso2.org I understand that fact. What I was asking is can we customize the authentication behavior. Are there extension points. Any way if there are not you can have a pretty defined user for each tenant same as we do for jenkins. Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 On Apr 1, 2015 7:14 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi danushka, The issue is with how the SOAP API for JIRA works. It requires admin username and password to establish a SOAP session, to create a project via the SOAP API. If we are to create a project on a user specified JIRA instance, the username and password (For that particular JIRA instance) are required. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 6:07 PM, Danushka Fernando danush...@wso2.com wrote: Hi Are there extension points in jira where we can extend authentication mechanism. BTW password is something we don't have. We have only username. Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 On Apr 1, 2015 4:25 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, I need few other clarifications as well. So far, I have been successful in creating a JIRA project via SOAP only. This SOAP client requires username and password for the Jira instance. So, if we want to allow users to create projects in their JIRA instance, we will have to request for username and password for JIRA instance. Is that okay? We will not store any username or password, but we'll need it to create a SOAP session. WDYT? Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 2:34 PM, Fathima Dilhasha dilha...@wso2.com wrote: The prices for cloud and server instances of JIRA are the same as mentioned in [1] https://www.atlassian.com/software/jira/pricing/?tab=cloud. [1]https://www.atlassian.com/software/jira/pricing/?tab=cloud Thanks. *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 2:31 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, IMO, creating separate JIRA instances for each tenant is not a feasible option, So regarding the projects that are created in the Jira instance of App Factory, User will have to undergo the limitation that, the tenant name would be appended at the end of project name. Is there any way we can avoid that? Thanks. Regards, Dilhasha *M.N.F.
Re: [Architecture] [App Factory] Jira Integration for WSO2 App Factory
Hi, IMO, creating separate JIRA instances for each tenant is not a feasible option, So regarding the projects that are created in the Jira instance of App Factory, User will have to undergo the limitation that, the tenant name would be appended at the end of project name. Is there any way we can avoid that? Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 2:25 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Anuruddha, Yeah I understand the issue with appending the tenant domain every time. +1 for the suggestion under 1) Regarding 2) that is when we create a Jira instance, AFAIK, whether we use an on-demand instance for App Factory or a Cloud instance, we would get the same problem of duplicate projects. Unless we create separate Jira Cloud instances for each tenant. WDYT? Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Tue, Mar 31, 2015 at 7:37 PM, Anuruddha Premalal anurud...@wso2.com wrote: Hi Fathima, I'm -1 in appending suffixes to project name at all the time. Jira is something we are going to expose to users. IMO we should allow them (at least for users with their own jira cloud) to go with what they wanted as the project name. You have to treat this as two separate scenarios. Jira could be available in the following ways; 1.) Cloud hosted on-demand jira offered by Atlassian. - This is hosted in a multitenant way (instance per customer) . You can read more about Atlassian cloud architecture [1] - In this case you don't actually need to append any suffix to project name. However if two tenants tries to share the same Cloud jira, we have to perform the project name validation and prompt user; there is already an existing project. 2.) AppFactory hosted single jira instance. - This is where we actually face the problem of duplicate project names; And it is because we don't have the containerized deployment for jira. How are we actually going to host jira? is another topic we need to discuss. Are we going to maintain a separate jira for AppFactory or are we going to go with Atlasian jira cloud?. What are the cost factors of each of them?. If we are going with Atlasian cloud we wan't face duplicate project name issue for multiple tenants. [1] https://developer.atlassian.com/static/connect/docs/latest/concepts/cloud-development.html#overview Regards, Anuruddha. On Tue, Mar 31, 2015 at 1:12 AM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, Okay, I got it now. So, there is no possibility of having similar named projects in a particular tenant right? If so appending tenant domain to the project name will be the best approach we can take. +1 for that. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Lanka* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Tue, Mar 31, 2015 at 1:36 PM, Manisha Gayathri mani...@wso2.com wrote: On Tue, Mar 31, 2015 at 1:31 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Mahesh, Yes, what I meant was App owner. Thanks for pointing out the scenario of having two similar named projects. AFAIK, we can not have projects with same name in a single Jira instance. +1 for Appending the App owners name at the end. That would solve that issue. Rather this should be tenant 'domain' of the app owner. If joh...@foo.com creates DummyProj, as the app then the JIRA project name will look like, fooDummyProj Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Lanka* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Tue, Mar 31, 2015 at 1:18 PM, Mahesh Chinthaka mahe...@wso2.com wrote: Hi Fathima, What did you mean by user's name ? Is it App owner ? If so +1 Just one clarification. Suppose there are 2 tenants A and B. Both have created applications named 'app1'. So will it be shown in jira as two projects with same name ? Or is it visible only within tenant's scope. What if we append tenant domain to application name and put it as project name. WDYT ? Thanks. On Tue, Mar 31, 2015 at 12:40 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, I have been successful in creating a project in a Jira instance via a SOAP client included in the issue tracking component in App Factory. Now, I have few clarifications regarding this project creation. When we create a Jira project for a specific Application in Appfactory, we have to specify a project name, and a project lead for that project. My suggestion is to use the application name as the project name and add a jira user with that user's name to our Jira instance. WDYT? Is there any better way we can do this? Thanks. Regards, Dilhasha
Re: [Architecture] [App Factory] Jira Integration for WSO2 App Factory
Hi Are there extension points in jira where we can extend authentication mechanism. BTW password is something we don't have. We have only username. Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 On Apr 1, 2015 4:25 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, I need few other clarifications as well. So far, I have been successful in creating a JIRA project via SOAP only. This SOAP client requires username and password for the Jira instance. So, if we want to allow users to create projects in their JIRA instance, we will have to request for username and password for JIRA instance. Is that okay? We will not store any username or password, but we'll need it to create a SOAP session. WDYT? Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 2:34 PM, Fathima Dilhasha dilha...@wso2.com wrote: The prices for cloud and server instances of JIRA are the same as mentioned in [1] https://www.atlassian.com/software/jira/pricing/?tab=cloud. [1]https://www.atlassian.com/software/jira/pricing/?tab=cloud Thanks. *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 2:31 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, IMO, creating separate JIRA instances for each tenant is not a feasible option, So regarding the projects that are created in the Jira instance of App Factory, User will have to undergo the limitation that, the tenant name would be appended at the end of project name. Is there any way we can avoid that? Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 2:25 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Anuruddha, Yeah I understand the issue with appending the tenant domain every time. +1 for the suggestion under 1) Regarding 2) that is when we create a Jira instance, AFAIK, whether we use an on-demand instance for App Factory or a Cloud instance, we would get the same problem of duplicate projects. Unless we create separate Jira Cloud instances for each tenant. WDYT? Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Tue, Mar 31, 2015 at 7:37 PM, Anuruddha Premalal anurud...@wso2.com wrote: Hi Fathima, I'm -1 in appending suffixes to project name at all the time. Jira is something we are going to expose to users. IMO we should allow them (at least for users with their own jira cloud) to go with what they wanted as the project name. You have to treat this as two separate scenarios. Jira could be available in the following ways; 1.) Cloud hosted on-demand jira offered by Atlassian. - This is hosted in a multitenant way (instance per customer) . You can read more about Atlassian cloud architecture [1] - In this case you don't actually need to append any suffix to project name. However if two tenants tries to share the same Cloud jira, we have to perform the project name validation and prompt user; there is already an existing project. 2.) AppFactory hosted single jira instance. - This is where we actually face the problem of duplicate project names; And it is because we don't have the containerized deployment for jira. How are we actually going to host jira? is another topic we need to discuss. Are we going to maintain a separate jira for AppFactory or are we going to go with Atlasian jira cloud?. What are the cost factors of each of them?. If we are going with Atlasian cloud we wan't face duplicate project name issue for multiple tenants. [1] https://developer.atlassian.com/static/connect/docs/latest/concepts/cloud-development.html#overview Regards, Anuruddha. On Tue, Mar 31, 2015 at 1:12 AM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, Okay, I got it now. So, there is no possibility of having similar named projects in a particular tenant right? If so appending tenant domain to the project name will be the best approach we can take. +1 for that. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Lanka* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Tue, Mar 31, 2015 at 1:36 PM, Manisha Gayathri mani...@wso2.com wrote: On Tue, Mar 31, 2015 at 1:31 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Mahesh, Yes, what I meant was App owner. Thanks for pointing out the scenario of having two similar named projects. AFAIK, we can not have projects with same name in a single Jira instance. +1 for Appending the App owners name at the end. That
Re: [Architecture] [App Factory] Jira Integration for WSO2 App Factory
Hi, I need few other clarifications as well. So far, I have been successful in creating a JIRA project via SOAP only. This SOAP client requires username and password for the Jira instance. So, if we want to allow users to create projects in their JIRA instance, we will have to request for username and password for JIRA instance. Is that okay? We will not store any username or password, but we'll need it to create a SOAP session. WDYT? Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 2:34 PM, Fathima Dilhasha dilha...@wso2.com wrote: The prices for cloud and server instances of JIRA are the same as mentioned in [1] https://www.atlassian.com/software/jira/pricing/?tab=cloud. [1]https://www.atlassian.com/software/jira/pricing/?tab=cloud Thanks. *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 2:31 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, IMO, creating separate JIRA instances for each tenant is not a feasible option, So regarding the projects that are created in the Jira instance of App Factory, User will have to undergo the limitation that, the tenant name would be appended at the end of project name. Is there any way we can avoid that? Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 2:25 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Anuruddha, Yeah I understand the issue with appending the tenant domain every time. +1 for the suggestion under 1) Regarding 2) that is when we create a Jira instance, AFAIK, whether we use an on-demand instance for App Factory or a Cloud instance, we would get the same problem of duplicate projects. Unless we create separate Jira Cloud instances for each tenant. WDYT? Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Tue, Mar 31, 2015 at 7:37 PM, Anuruddha Premalal anurud...@wso2.com wrote: Hi Fathima, I'm -1 in appending suffixes to project name at all the time. Jira is something we are going to expose to users. IMO we should allow them (at least for users with their own jira cloud) to go with what they wanted as the project name. You have to treat this as two separate scenarios. Jira could be available in the following ways; 1.) Cloud hosted on-demand jira offered by Atlassian. - This is hosted in a multitenant way (instance per customer) . You can read more about Atlassian cloud architecture [1] - In this case you don't actually need to append any suffix to project name. However if two tenants tries to share the same Cloud jira, we have to perform the project name validation and prompt user; there is already an existing project. 2.) AppFactory hosted single jira instance. - This is where we actually face the problem of duplicate project names; And it is because we don't have the containerized deployment for jira. How are we actually going to host jira? is another topic we need to discuss. Are we going to maintain a separate jira for AppFactory or are we going to go with Atlasian jira cloud?. What are the cost factors of each of them?. If we are going with Atlasian cloud we wan't face duplicate project name issue for multiple tenants. [1] https://developer.atlassian.com/static/connect/docs/latest/concepts/cloud-development.html#overview Regards, Anuruddha. On Tue, Mar 31, 2015 at 1:12 AM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, Okay, I got it now. So, there is no possibility of having similar named projects in a particular tenant right? If so appending tenant domain to the project name will be the best approach we can take. +1 for that. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Lanka* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Tue, Mar 31, 2015 at 1:36 PM, Manisha Gayathri mani...@wso2.com wrote: On Tue, Mar 31, 2015 at 1:31 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Mahesh, Yes, what I meant was App owner. Thanks for pointing out the scenario of having two similar named projects. AFAIK, we can not have projects with same name in a single Jira instance. +1 for Appending the App owners name at the end. That would solve that issue. Rather this should be tenant 'domain' of the app owner. If joh...@foo.com creates DummyProj, as the app then the JIRA project name will look like, fooDummyProj Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Lanka* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77
Re: [Architecture] [App Factory] Jira Integration for WSO2 App Factory
Hi danushka, The issue is with how the SOAP API for JIRA works. It requires admin username and password to establish a SOAP session, to create a project via the SOAP API. If we are to create a project on a user specified JIRA instance, the username and password (For that particular JIRA instance) are required. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 6:07 PM, Danushka Fernando danush...@wso2.com wrote: Hi Are there extension points in jira where we can extend authentication mechanism. BTW password is something we don't have. We have only username. Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 On Apr 1, 2015 4:25 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, I need few other clarifications as well. So far, I have been successful in creating a JIRA project via SOAP only. This SOAP client requires username and password for the Jira instance. So, if we want to allow users to create projects in their JIRA instance, we will have to request for username and password for JIRA instance. Is that okay? We will not store any username or password, but we'll need it to create a SOAP session. WDYT? Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 2:34 PM, Fathima Dilhasha dilha...@wso2.com wrote: The prices for cloud and server instances of JIRA are the same as mentioned in [1] https://www.atlassian.com/software/jira/pricing/?tab=cloud. [1]https://www.atlassian.com/software/jira/pricing/?tab=cloud Thanks. *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 2:31 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, IMO, creating separate JIRA instances for each tenant is not a feasible option, So regarding the projects that are created in the Jira instance of App Factory, User will have to undergo the limitation that, the tenant name would be appended at the end of project name. Is there any way we can avoid that? Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 2:25 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Anuruddha, Yeah I understand the issue with appending the tenant domain every time. +1 for the suggestion under 1) Regarding 2) that is when we create a Jira instance, AFAIK, whether we use an on-demand instance for App Factory or a Cloud instance, we would get the same problem of duplicate projects. Unless we create separate Jira Cloud instances for each tenant. WDYT? Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Tue, Mar 31, 2015 at 7:37 PM, Anuruddha Premalal anurud...@wso2.com wrote: Hi Fathima, I'm -1 in appending suffixes to project name at all the time. Jira is something we are going to expose to users. IMO we should allow them (at least for users with their own jira cloud) to go with what they wanted as the project name. You have to treat this as two separate scenarios. Jira could be available in the following ways; 1.) Cloud hosted on-demand jira offered by Atlassian. - This is hosted in a multitenant way (instance per customer) . You can read more about Atlassian cloud architecture [1] - In this case you don't actually need to append any suffix to project name. However if two tenants tries to share the same Cloud jira, we have to perform the project name validation and prompt user; there is already an existing project. 2.) AppFactory hosted single jira instance. - This is where we actually face the problem of duplicate project names; And it is because we don't have the containerized deployment for jira. How are we actually going to host jira? is another topic we need to discuss. Are we going to maintain a separate jira for AppFactory or are we going to go with Atlasian jira cloud?. What are the cost factors of each of them?. If we are going with Atlasian cloud we wan't face duplicate project name issue for multiple tenants. [1] https://developer.atlassian.com/static/connect/docs/latest/concepts/cloud-development.html#overview Regards, Anuruddha. On Tue, Mar 31, 2015 at 1:12 AM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, Okay, I got it now. So, there is no possibility of having similar named projects in a particular tenant right? If so appending tenant domain to the project name will be the best approach we can take. +1 for that. Thanks.
Re: [Architecture] [App Factory] Jira Integration for WSO2 App Factory
I understand that fact. What I was asking is can we customize the authentication behavior. Are there extension points. Any way if there are not you can have a pretty defined user for each tenant same as we do for jenkins. Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 On Apr 1, 2015 7:14 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi danushka, The issue is with how the SOAP API for JIRA works. It requires admin username and password to establish a SOAP session, to create a project via the SOAP API. If we are to create a project on a user specified JIRA instance, the username and password (For that particular JIRA instance) are required. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 6:07 PM, Danushka Fernando danush...@wso2.com wrote: Hi Are there extension points in jira where we can extend authentication mechanism. BTW password is something we don't have. We have only username. Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 On Apr 1, 2015 4:25 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, I need few other clarifications as well. So far, I have been successful in creating a JIRA project via SOAP only. This SOAP client requires username and password for the Jira instance. So, if we want to allow users to create projects in their JIRA instance, we will have to request for username and password for JIRA instance. Is that okay? We will not store any username or password, but we'll need it to create a SOAP session. WDYT? Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 2:34 PM, Fathima Dilhasha dilha...@wso2.com wrote: The prices for cloud and server instances of JIRA are the same as mentioned in [1] https://www.atlassian.com/software/jira/pricing/?tab=cloud. [1]https://www.atlassian.com/software/jira/pricing/?tab=cloud Thanks. *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 2:31 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, IMO, creating separate JIRA instances for each tenant is not a feasible option, So regarding the projects that are created in the Jira instance of App Factory, User will have to undergo the limitation that, the tenant name would be appended at the end of project name. Is there any way we can avoid that? Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 2:25 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Anuruddha, Yeah I understand the issue with appending the tenant domain every time. +1 for the suggestion under 1) Regarding 2) that is when we create a Jira instance, AFAIK, whether we use an on-demand instance for App Factory or a Cloud instance, we would get the same problem of duplicate projects. Unless we create separate Jira Cloud instances for each tenant. WDYT? Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Tue, Mar 31, 2015 at 7:37 PM, Anuruddha Premalal anurud...@wso2.com wrote: Hi Fathima, I'm -1 in appending suffixes to project name at all the time. Jira is something we are going to expose to users. IMO we should allow them (at least for users with their own jira cloud) to go with what they wanted as the project name. You have to treat this as two separate scenarios. Jira could be available in the following ways; 1.) Cloud hosted on-demand jira offered by Atlassian. - This is hosted in a multitenant way (instance per customer) . You can read more about Atlassian cloud architecture [1] - In this case you don't actually need to append any suffix to project name. However if two tenants tries to share the same Cloud jira, we have to perform the project name validation and prompt user; there is already an existing project. 2.) AppFactory hosted single jira instance. - This is where we actually face the problem of duplicate project names; And it is because we don't have the containerized deployment for jira. How are we actually going to host jira? is another topic we need to discuss. Are we going to maintain a separate jira for AppFactory or are we going to go with Atlasian jira cloud?. What are the cost factors of each of them?. If we are going with Atlasian cloud we wan't face duplicate project name issue for multiple tenants. [1]
Re: [Architecture] [App Factory] Jira Integration for WSO2 App Factory
/s/pretty/pre Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 From: Danushka Fernando Sent: Wednesday, April 1, 2015 7:30 PM To: architecture I understand that fact. What I was asking is can we customize the authentication behavior. Are there extension points. Any way if there are not you can have a pretty defined user for each tenant same as we do for jenkins. Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 On Apr 1, 2015 7:14 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi danushka, The issue is with how the SOAP API for JIRA works. It requires admin username and password to establish a SOAP session, to create a project via the SOAP API. If we are to create a project on a user specified JIRA instance, the username and password (For that particular JIRA instance) are required. Thanks. Regards, Dilhasha M.N.F. Dilhasha Software Engineering Intern | WSO2 Inc. email : dilha...@wso2.com mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 6:07 PM, Danushka Fernando danush...@wso2.com wrote: Hi Are there extension points in jira where we can extend authentication mechanism. BTW password is something we don't have. We have only username. Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 On Apr 1, 2015 4:25 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, I need few other clarifications as well. So far, I have been successful in creating a JIRA project via SOAP only. This SOAP client requires username and password for the Jira instance. So, if we want to allow users to create projects in their JIRA instance, we will have to request for username and password for JIRA instance. Is that okay? We will not store any username or password, but we'll need it to create a SOAP session. WDYT? Thanks. Regards, Dilhasha M.N.F. Dilhasha Software Engineering Intern | WSO2 Inc. email : dilha...@wso2.com mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 2:34 PM, Fathima Dilhasha dilha...@wso2.com wrote: The prices for cloud and server instances of JIRA are the same as mentioned in [1]. [1]https://www.atlassian.com/software/jira/pricing/?tab=cloud Thanks. M.N.F. Dilhasha Software Engineering Intern | WSO2 Inc. email : dilha...@wso2.com mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 2:31 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, IMO, creating separate JIRA instances for each tenant is not a feasible option, So regarding the projects that are created in the Jira instance of App Factory, User will have to undergo the limitation that, the tenant name would be appended at the end of project name. Is there any way we can avoid that? Thanks. Regards, Dilhasha M.N.F. Dilhasha Software Engineering Intern | WSO2 Inc. email : dilha...@wso2.com mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 2:25 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Anuruddha, Yeah I understand the issue with appending the tenant domain every time. +1 for the suggestion under 1) Regarding 2) that is when we create a Jira instance, AFAIK, whether we use an on-demand instance for App Factory or a Cloud instance, we would get the same problem of duplicate projects. Unless we create separate Jira Cloud instances for each tenant. WDYT? Thanks. Regards, Dilhasha M.N.F. Dilhasha Software Engineering Intern | WSO2 Inc. email : dilha...@wso2.com mobile : +94 77 8449321 On Tue, Mar 31, 2015 at 7:37 PM, Anuruddha Premalal anurud...@wso2.com wrote: Hi Fathima, I'm -1 in appending suffixes to project name at all the time. Jira is something we are going to expose to users. IMO we should allow them (at least for users with their own jira cloud) to go with what they wanted as the project name. You have to treat this as two separate scenarios. Jira could be available in the following ways; 1.) Cloud hosted on-demand jira offered by Atlassian. - This is hosted in a multitenant way (instance per customer) . You can read more about Atlassian cloud architecture [1] - In this case you don't actually need to append any suffix to project name. However if two tenants tries to share the same Cloud jira, we have to perform the project name validation and prompt user; there is already an existing project. 2.) AppFactory hosted single jira instance. - This is where we actually face the problem of duplicate project names; And it is because we don't have the containerized deployment for jira. How are we actually going to host jira? is another topic we need to discuss. Are we going to maintain a separate jira for AppFactory or are we going to go with Atlasian jira cloud?. What are the cost factors of each of them?. If we
Re: [Architecture] [App Factory] Jira Integration for WSO2 App Factory
Hi, Okay, now I understand your first question. AFAIK, there is no way to customize authentication behavior, in a way that we can allow to have similar project names for different tenants. We can have groups of users and manage visibility of each project on a single JIRA instance, among users in that instance as specified in [1] https://confluence.atlassian.com/display/Cloud/Managing+project+visibility . What you are suggesting is to map a user in JIRA to a particular tenant in App Factory, is it? [1] https://confluence.atlassian.com/display/Cloud/Managing+project+visibility Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 7:56 PM, danush...@wso2.com wrote: /s/pretty/pre Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 *From:* Danushka Fernando danush...@wso2.com *Sent:* Wednesday, April 1, 2015 7:30 PM *To:* architecture architecture@wso2.org I understand that fact. What I was asking is can we customize the authentication behavior. Are there extension points. Any way if there are not you can have a pretty defined user for each tenant same as we do for jenkins. Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 On Apr 1, 2015 7:14 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi danushka, The issue is with how the SOAP API for JIRA works. It requires admin username and password to establish a SOAP session, to create a project via the SOAP API. If we are to create a project on a user specified JIRA instance, the username and password (For that particular JIRA instance) are required. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 6:07 PM, Danushka Fernando danush...@wso2.com wrote: Hi Are there extension points in jira where we can extend authentication mechanism. BTW password is something we don't have. We have only username. Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 On Apr 1, 2015 4:25 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, I need few other clarifications as well. So far, I have been successful in creating a JIRA project via SOAP only. This SOAP client requires username and password for the Jira instance. So, if we want to allow users to create projects in their JIRA instance, we will have to request for username and password for JIRA instance. Is that okay? We will not store any username or password, but we'll need it to create a SOAP session. WDYT? Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 2:34 PM, Fathima Dilhasha dilha...@wso2.com wrote: The prices for cloud and server instances of JIRA are the same as mentioned in [1] https://www.atlassian.com/software/jira/pricing/?tab=cloud. [1]https://www.atlassian.com/software/jira/pricing/?tab=cloud Thanks. *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 2:31 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, IMO, creating separate JIRA instances for each tenant is not a feasible option, So regarding the projects that are created in the Jira instance of App Factory, User will have to undergo the limitation that, the tenant name would be appended at the end of project name. Is there any way we can avoid that? Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 2:25 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Anuruddha, Yeah I understand the issue with appending the tenant domain every time. +1 for the suggestion under 1) Regarding 2) that is when we create a Jira instance, AFAIK, whether we use an on-demand instance for App Factory or a Cloud instance, we would get the same problem of duplicate projects. Unless we create separate Jira Cloud instances for each tenant. WDYT? Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Tue, Mar 31, 2015 at 7:37 PM, Anuruddha Premalal anurud...@wso2.com wrote: Hi Fathima, I'm -1 in appending suffixes to project name at all the time. Jira is something we are going to expose to users. IMO we should allow them (at least for users with their own jira cloud) to go with what they wanted as the project name. You have to treat this as two separate
Re: [Architecture] [App Factory] Jira Integration for WSO2 App Factory
Hi Punnadi, We cannot store credentials in a configuration file since this is a per application configuration. Regards, Anuruddha. On Wed, Apr 1, 2015 at 9:43 AM, Punnadi Gunarathna punn...@wso2.com wrote: Hi Fathima, Can't we store the credentials in a configuration file, which are required to create the JIRA instance? If that is possible, We can make use of Secure Vault to secure the plain text password. WDYT? On Apr 1, 2015 8:04 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, Okay, now I understand your first question. AFAIK, there is no way to customize authentication behavior, in a way that we can allow to have similar project names for different tenants. We can have groups of users and manage visibility of each project on a single JIRA instance, among users in that instance as specified in [1] https://confluence.atlassian.com/display/Cloud/Managing+project+visibility . What you are suggesting is to map a user in JIRA to a particular tenant in App Factory, is it? [1] https://confluence.atlassian.com/display/Cloud/Managing+project+visibility Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 7:56 PM, danush...@wso2.com wrote: /s/pretty/pre Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 *From:* Danushka Fernando danush...@wso2.com *Sent:* Wednesday, April 1, 2015 7:30 PM *To:* architecture architecture@wso2.org I understand that fact. What I was asking is can we customize the authentication behavior. Are there extension points. Any way if there are not you can have a pretty defined user for each tenant same as we do for jenkins. Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 On Apr 1, 2015 7:14 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi danushka, The issue is with how the SOAP API for JIRA works. It requires admin username and password to establish a SOAP session, to create a project via the SOAP API. If we are to create a project on a user specified JIRA instance, the username and password (For that particular JIRA instance) are required. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 6:07 PM, Danushka Fernando danush...@wso2.com wrote: Hi Are there extension points in jira where we can extend authentication mechanism. BTW password is something we don't have. We have only username. Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 On Apr 1, 2015 4:25 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, I need few other clarifications as well. So far, I have been successful in creating a JIRA project via SOAP only. This SOAP client requires username and password for the Jira instance. So, if we want to allow users to create projects in their JIRA instance, we will have to request for username and password for JIRA instance. Is that okay? We will not store any username or password, but we'll need it to create a SOAP session. WDYT? Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 2:34 PM, Fathima Dilhasha dilha...@wso2.com wrote: The prices for cloud and server instances of JIRA are the same as mentioned in [1] https://www.atlassian.com/software/jira/pricing/?tab=cloud. [1]https://www.atlassian.com/software/jira/pricing/?tab=cloud Thanks. *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 2:31 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, IMO, creating separate JIRA instances for each tenant is not a feasible option, So regarding the projects that are created in the Jira instance of App Factory, User will have to undergo the limitation that, the tenant name would be appended at the end of project name. Is there any way we can avoid that? Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 2:25 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Anuruddha, Yeah I understand the issue with appending the tenant domain every time. +1 for the suggestion under 1) Regarding 2) that is when we create a Jira instance, AFAIK, whether we use an on-demand instance for App Factory or a Cloud instance, we would get the same problem of duplicate projects. Unless we create separate Jira Cloud instances for each tenant. WDYT? Thanks. Regards, Dilhasha
Re: [Architecture] [App Factory] Jira Integration for WSO2 App Factory
Hi Fathima, Can't we store the credentials in a configuration file, which are required to create the JIRA instance? If that is possible, We can make use of Secure Vault to secure the plain text password. WDYT? On Apr 1, 2015 8:04 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, Okay, now I understand your first question. AFAIK, there is no way to customize authentication behavior, in a way that we can allow to have similar project names for different tenants. We can have groups of users and manage visibility of each project on a single JIRA instance, among users in that instance as specified in [1] https://confluence.atlassian.com/display/Cloud/Managing+project+visibility . What you are suggesting is to map a user in JIRA to a particular tenant in App Factory, is it? [1] https://confluence.atlassian.com/display/Cloud/Managing+project+visibility Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 7:56 PM, danush...@wso2.com wrote: /s/pretty/pre Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 *From:* Danushka Fernando danush...@wso2.com *Sent:* Wednesday, April 1, 2015 7:30 PM *To:* architecture architecture@wso2.org I understand that fact. What I was asking is can we customize the authentication behavior. Are there extension points. Any way if there are not you can have a pretty defined user for each tenant same as we do for jenkins. Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 On Apr 1, 2015 7:14 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi danushka, The issue is with how the SOAP API for JIRA works. It requires admin username and password to establish a SOAP session, to create a project via the SOAP API. If we are to create a project on a user specified JIRA instance, the username and password (For that particular JIRA instance) are required. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 6:07 PM, Danushka Fernando danush...@wso2.com wrote: Hi Are there extension points in jira where we can extend authentication mechanism. BTW password is something we don't have. We have only username. Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 On Apr 1, 2015 4:25 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, I need few other clarifications as well. So far, I have been successful in creating a JIRA project via SOAP only. This SOAP client requires username and password for the Jira instance. So, if we want to allow users to create projects in their JIRA instance, we will have to request for username and password for JIRA instance. Is that okay? We will not store any username or password, but we'll need it to create a SOAP session. WDYT? Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 2:34 PM, Fathima Dilhasha dilha...@wso2.com wrote: The prices for cloud and server instances of JIRA are the same as mentioned in [1] https://www.atlassian.com/software/jira/pricing/?tab=cloud. [1]https://www.atlassian.com/software/jira/pricing/?tab=cloud Thanks. *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 2:31 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, IMO, creating separate JIRA instances for each tenant is not a feasible option, So regarding the projects that are created in the Jira instance of App Factory, User will have to undergo the limitation that, the tenant name would be appended at the end of project name. Is there any way we can avoid that? Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Wed, Apr 1, 2015 at 2:25 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Anuruddha, Yeah I understand the issue with appending the tenant domain every time. +1 for the suggestion under 1) Regarding 2) that is when we create a Jira instance, AFAIK, whether we use an on-demand instance for App Factory or a Cloud instance, we would get the same problem of duplicate projects. Unless we create separate Jira Cloud instances for each tenant. WDYT? Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Inc.* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Tue, Mar 31, 2015 at 7:37 PM, Anuruddha Premalal anurud...@wso2.com wrote:
Re: [Architecture] [App Factory] Jira Integration for WSO2 App Factory
Hi Fathima, What did you mean by user's name ? Is it App owner ? If so +1 Just one clarification. Suppose there are 2 tenants A and B. Both have created applications named 'app1'. So will it be shown in jira as two projects with same name ? Or is it visible only within tenant's scope. What if we append tenant domain to application name and put it as project name. WDYT ? Thanks. On Tue, Mar 31, 2015 at 12:40 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, I have been successful in creating a project in a Jira instance via a SOAP client included in the issue tracking component in App Factory. Now, I have few clarifications regarding this project creation. When we create a Jira project for a specific Application in Appfactory, we have to specify a project name, and a project lead for that project. My suggestion is to use the application name as the project name and add a jira user with that user's name to our Jira instance. WDYT? Is there any better way we can do this? Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Lanka* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- *Mahesh Chinthaka Vidanagama* | Software Engineer WSO2, Inc | lean. enterprise. middleware. #20, Palm Grove, Colombo 03, Sri Lanka Mobile: +94 71 63 63 083 | Work: +94 112 145 345 Email: mahe...@wso2.com | Web: www.wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [App Factory] Jira Integration for WSO2 App Factory
Hi, Okay, I got it now. So, there is no possibility of having similar named projects in a particular tenant right? If so appending tenant domain to the project name will be the best approach we can take. +1 for that. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Lanka* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Tue, Mar 31, 2015 at 1:36 PM, Manisha Gayathri mani...@wso2.com wrote: On Tue, Mar 31, 2015 at 1:31 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Mahesh, Yes, what I meant was App owner. Thanks for pointing out the scenario of having two similar named projects. AFAIK, we can not have projects with same name in a single Jira instance. +1 for Appending the App owners name at the end. That would solve that issue. Rather this should be tenant 'domain' of the app owner. If joh...@foo.com creates DummyProj, as the app then the JIRA project name will look like, fooDummyProj Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Lanka* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Tue, Mar 31, 2015 at 1:18 PM, Mahesh Chinthaka mahe...@wso2.com wrote: Hi Fathima, What did you mean by user's name ? Is it App owner ? If so +1 Just one clarification. Suppose there are 2 tenants A and B. Both have created applications named 'app1'. So will it be shown in jira as two projects with same name ? Or is it visible only within tenant's scope. What if we append tenant domain to application name and put it as project name. WDYT ? Thanks. On Tue, Mar 31, 2015 at 12:40 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, I have been successful in creating a project in a Jira instance via a SOAP client included in the issue tracking component in App Factory. Now, I have few clarifications regarding this project creation. When we create a Jira project for a specific Application in Appfactory, we have to specify a project name, and a project lead for that project. My suggestion is to use the application name as the project name and add a jira user with that user's name to our Jira instance. WDYT? Is there any better way we can do this? Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Lanka* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- *Mahesh Chinthaka Vidanagama* | Software Engineer WSO2, Inc | lean. enterprise. middleware. #20, Palm Grove, Colombo 03, Sri Lanka Mobile: +94 71 63 63 083 | Work: +94 112 145 345 Email: mahe...@wso2.com | Web: www.wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- ~Regards *Manisha Eleperuma* Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware *blog: http://manisha-eleperuma.blogspot.com/ http://manisha-eleperuma.blogspot.com/* *mobile: +94 71 8279777 %2B94%2071%208279777* ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [App Factory] Jira Integration for WSO2 App Factory
On Tue, Mar 31, 2015 at 1:31 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Mahesh, Yes, what I meant was App owner. Thanks for pointing out the scenario of having two similar named projects. AFAIK, we can not have projects with same name in a single Jira instance. +1 for Appending the App owners name at the end. That would solve that issue. Rather this should be tenant 'domain' of the app owner. If joh...@foo.com creates DummyProj, as the app then the JIRA project name will look like, fooDummyProj Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Lanka* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Tue, Mar 31, 2015 at 1:18 PM, Mahesh Chinthaka mahe...@wso2.com wrote: Hi Fathima, What did you mean by user's name ? Is it App owner ? If so +1 Just one clarification. Suppose there are 2 tenants A and B. Both have created applications named 'app1'. So will it be shown in jira as two projects with same name ? Or is it visible only within tenant's scope. What if we append tenant domain to application name and put it as project name. WDYT ? Thanks. On Tue, Mar 31, 2015 at 12:40 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, I have been successful in creating a project in a Jira instance via a SOAP client included in the issue tracking component in App Factory. Now, I have few clarifications regarding this project creation. When we create a Jira project for a specific Application in Appfactory, we have to specify a project name, and a project lead for that project. My suggestion is to use the application name as the project name and add a jira user with that user's name to our Jira instance. WDYT? Is there any better way we can do this? Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Lanka* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- *Mahesh Chinthaka Vidanagama* | Software Engineer WSO2, Inc | lean. enterprise. middleware. #20, Palm Grove, Colombo 03, Sri Lanka Mobile: +94 71 63 63 083 | Work: +94 112 145 345 Email: mahe...@wso2.com | Web: www.wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- ~Regards *Manisha Eleperuma* Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware *blog: http://manisha-eleperuma.blogspot.com/ http://manisha-eleperuma.blogspot.com/* *mobile: +94 71 8279777* ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [App Factory] Jira Integration for WSO2 App Factory
Hi Fathima, I'm -1 in appending suffixes to project name at all the time. Jira is something we are going to expose to users. IMO we should allow them (at least for users with their own jira cloud) to go with what they wanted as the project name. You have to treat this as two separate scenarios. Jira could be available in the following ways; 1.) Cloud hosted on-demand jira offered by Atlassian. - This is hosted in a multitenant way (instance per customer) . You can read more about Atlassian cloud architecture [1] - In this case you don't actually need to append any suffix to project name. However if two tenants tries to share the same Cloud jira, we have to perform the project name validation and prompt user; there is already an existing project. 2.) AppFactory hosted single jira instance. - This is where we actually face the problem of duplicate project names; And it is because we don't have the containerized deployment for jira. How are we actually going to host jira? is another topic we need to discuss. Are we going to maintain a separate jira for AppFactory or are we going to go with Atlasian jira cloud?. What are the cost factors of each of them?. If we are going with Atlasian cloud we wan't face duplicate project name issue for multiple tenants. [1] https://developer.atlassian.com/static/connect/docs/latest/concepts/cloud-development.html#overview Regards, Anuruddha. On Tue, Mar 31, 2015 at 1:12 AM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, Okay, I got it now. So, there is no possibility of having similar named projects in a particular tenant right? If so appending tenant domain to the project name will be the best approach we can take. +1 for that. Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Lanka* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Tue, Mar 31, 2015 at 1:36 PM, Manisha Gayathri mani...@wso2.com wrote: On Tue, Mar 31, 2015 at 1:31 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi Mahesh, Yes, what I meant was App owner. Thanks for pointing out the scenario of having two similar named projects. AFAIK, we can not have projects with same name in a single Jira instance. +1 for Appending the App owners name at the end. That would solve that issue. Rather this should be tenant 'domain' of the app owner. If joh...@foo.com creates DummyProj, as the app then the JIRA project name will look like, fooDummyProj Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Lanka* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 On Tue, Mar 31, 2015 at 1:18 PM, Mahesh Chinthaka mahe...@wso2.com wrote: Hi Fathima, What did you mean by user's name ? Is it App owner ? If so +1 Just one clarification. Suppose there are 2 tenants A and B. Both have created applications named 'app1'. So will it be shown in jira as two projects with same name ? Or is it visible only within tenant's scope. What if we append tenant domain to application name and put it as project name. WDYT ? Thanks. On Tue, Mar 31, 2015 at 12:40 PM, Fathima Dilhasha dilha...@wso2.com wrote: Hi, I have been successful in creating a project in a Jira instance via a SOAP client included in the issue tracking component in App Factory. Now, I have few clarifications regarding this project creation. When we create a Jira project for a specific Application in Appfactory, we have to specify a project name, and a project lead for that project. My suggestion is to use the application name as the project name and add a jira user with that user's name to our Jira instance. WDYT? Is there any better way we can do this? Thanks. Regards, Dilhasha *M.N.F. Dilhasha* Software Engineering Intern | *WSO2 Lanka* email : *dilha...@wso2.com dilha...@wso2.com*mobile : +94 77 8449321 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- *Mahesh Chinthaka Vidanagama* | Software Engineer WSO2, Inc | lean. enterprise. middleware. #20, Palm Grove, Colombo 03, Sri Lanka Mobile: +94 71 63 63 083 | Work: +94 112 145 345 Email: mahe...@wso2.com | Web: www.wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- ~Regards *Manisha Eleperuma* Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware *blog: http://manisha-eleperuma.blogspot.com/ http://manisha-eleperuma.blogspot.com/* *mobile: +94 71 8279777 %2B94%2071%208279777* ___ Architecture mailing list Architecture@wso2.org
