/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" <[email protected]> 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   : [email protected]
mobile : +94 77 8449321


On Wed, Apr 1, 2015 at 6:07 PM, Danushka Fernando <[email protected]> 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" <[email protected]> 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   : [email protected]
mobile : +94 77 8449321


On Wed, Apr 1, 2015 at 2:34 PM, Fathima Dilhasha <[email protected]> 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   : [email protected]
mobile : +94 77 8449321




On Wed, Apr 1, 2015 at 2:31 PM, Fathima Dilhasha <[email protected]> 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   : [email protected]
mobile : +94 77 8449321




On Wed, Apr 1, 2015 at 2:25 PM, Fathima Dilhasha <[email protected]> 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   : [email protected]
mobile : +94 77 8449321




On Tue, Mar 31, 2015 at 7:37 PM, Anuruddha Premalal <[email protected]> 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 <[email protected]> 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   : [email protected]
mobile : +94 77 8449321




On Tue, Mar 31, 2015 at 1:36 PM, Manisha Gayathri <[email protected]> wrote:






On Tue, Mar 31, 2015 at 1:31 PM, Fathima Dilhasha <[email protected]> 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 [email protected] 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   : [email protected]
mobile : +94 77 8449321




On Tue, Mar 31, 2015 at 1:18 PM, Mahesh Chinthaka <[email protected]> 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 <[email protected]> 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   : [email protected]
mobile : +94 77 8449321

_______________________________________________
Architecture mailing list
[email protected]
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: [email protected] | Web: www.wso2.com


_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture



_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture






-- 


~Regards
Manisha Eleperuma
Software Engineer

WSO2, Inc.: http://wso2.com

lean.enterprise.middleware




blog:      http://manisha-eleperuma.blogspot.com/

mobile:  +94 71 8279777




_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture



_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture






-- 


Anuruddha Premalal

Software Eng. | WSO2 Inc.

Mobile : +94710461070

Web site : www.regilandvalley.com




_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture






_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture


_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture



_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to