[Fiware-jira] FW: Query on On-demand JIRA instance in evaluation period - {818372}

[MANUEL ESCRICHE VICENTE]

From: sales at atlassian.com [mailto:sales at atlassian.com]
Sent: miércoles, 21 de agosto de 2013 0:53
To: MANUEL ESCRICHE VICENTE
Cc: MIGUEL CARRILLO PACHECO
Subject: RE: Query on On-demand JIRA instance in evaluation period - {818372}

## Reply ABOVE THIS LINE to add a note to this request ##


Hi Manuel,

Thanks for the email and allow me to step in for Anna here.

1. Single sign-on. We need to setup a solution that allow our users to have a single sign-on against both our collaborative working environment, where users get authenticated, and the on-demand JIRA instance. However, it seems we havent been able to find the right solution. We wonder whether its only possible to accomplish it using a hosted (downloaded) JIRA instance. We would appreciate to have your feedback on this issue since this feature is very important for our collaborative working environment

Though Atlassian OnDemand does provide single sign on between the applications you've activated within your OnDemand suite (for example if you were using JIRA alongside our content collaboration tool Confluence), single sign on with third party or locally hosted applications and local directories (LDAP) is not supported at this time. With a Download instance of JIRA, it is possible to use Atlassian Crowd<https://www.atlassian.com/software/crowd/overview>, our single sign on and unified identity management tool. Crowd would allow you to control user access and single sign on to its connected applications. It includes connectors to JIRA and Atlassian applications out of box, and it is possible to build a custom connector for other non-Atlassian apps with Crowd: see Integrating Crowd with a Custom Application<http://confluence.atlassian.com/display/CROWD/Integrating+Crowd+with+a+Custom+Application>. To set expectations, it sounds like it can usually take someone who knows what they are doing a day or two to Create a Crowd Client for your Custom Application<https://developer.atlassian.com/display/CROWDDEV/Creating+a+Crowd+Client+for+your+Custom+Application>. Alternatively, customers have had varying degrees of success integrating JIRA with other SSO platforms: see this community article<https://confluence.atlassian.com/display/DEV/Single+Sign-on+Integration+with+JIRA+and+Confluence> for further info.

2. It would be critical for us to confirm whether it is possible to export the current content from the on-demand JIRA to a downloaded one, and additionally knowing whether the reverse migration (from a downloaded JIRA to the on-demand JIRA) is also possible.

Both possible.

OnDemand to Download

OnDemand subscribers can migrate their data from an OnDemand instance to an installed instance.

You'll need to export your data from OnDemand, before importing it into your installed instance running a compatible version of the software.

When you wish to initiate a migration to a Download edition, simply utilize our customer-facing Backup Manager<https://confluence.atlassian.com/display/AOD/Backing+up+and+exporting+data> to retrieve a full JIRA backup. Once you have the backup, it is simply a matter of restoring the data<http://confluence.atlassian.com/display/JIRA/Restoring+Data> into a local version of JIRA.

Download to OnDemand

You can easily migrate from behind-the-firewall to OnDemand. You will first need to upgrade your application versions to match the current OnDemand application version<https://confluence.atlassian.com/display/AOD/Atlassian+OnDemand+Application+Versions>, then take backups of your JIRA and/or Confluence instance and use our Import Wizards<http://confluence.atlassian.com/display/AOD/Importing+Data> to restore your data in a new OnDemand instance<https://my.atlassian.com/ondemand/signup/jira>.

If you come across any technical difficulties during either type of migration, please feel free to file a support ticket<http://support.atlassian.com>. If you have never used our support portal before, you will need to sign up<https://support.atlassian.com/secure/Signup!default.jspa> first.

I hope this clarifies, Manuel. Please let us know if we can further assist.


Cheers,
Jason Caragan
Product Advocate Team Lead

--

Our biggest user conference yet: Atlassian Summit 2013<http://summit.atlassian.com/?utm_source=advocates-email-signature&utm_medium=email&utm_campaign=summit2013>! October 1-3 in San Francisco, CA

sales at atlassian.com<mailto:sales at atlassian.com>
+1 415 701 1110 (San Francisco, USA)
+61 2 9262 1443 (Sydney, Australia)
+31 20 796 0060 (Amsterdam, Netherlands)
----
MANUEL ESCRICHE VICENTE - mev at tid.es<mailto:mev at tid.es> - 19 Aug 2013, 06:36 AM PDT
Dear Atlassian team,

I am writing to you to clarify some questions that came up during the evaluation period for the JIRA instance https://fi-ware.atlassian.net , whose evaluation period is coming to an end in the coming days.

Despite the work done during the evaluation period, we have still some uncertainties on how to solve a couple of issues. Your help or advice would be appreciated:

  1.  Single sign-on. We need to setup a solution that allow our users to have a single sign-on against both our collaborative working environment, where users get authenticated,  and the on-demand JIRA instance.    However, it seems we haven't been able to find the right solution. We wonder whether it's only possible to accomplish it using a hosted (downloaded) JIRA instance. We would appreciate to have your feedback on this issue since this feature is very important for our collaborative working environment
  2.  Migration from on demand to downloaded instance. Since we haven't been able to fix the single sign-on properly with the on-demand instance, we're thinking of buying a downloaded JIRA instead of the on-demand one. We would appreciate the possibility of doing it if the on demand setting does not turn out to be feasible.  It would be critical for us to confirm whether it is possible to export the current content from the on-demand JIRA to a downloaded one, and additionally knowing whether the reverse migration (from a downloaded JIRA to the on-demand JIRA) is also possible.

Since it doesn't seem obvious how to solve these issues in very short time, I need to request an extension for the evaluation period. It would certainly help us fixing the issues above properly, and would very much be appreciated.

We would appreciate a quick reaction.

Thanks in advance.
Kind regards,
Manuel


----------------------------
Manuel Escriche Vicente
Agile Project Manager/Leader
FI-WARE Initiative
Telefónica Digital
Parque Tecnológico
C/ Abraham Zacuto, 10
47151 - Boecillo
Valladolid - Spain
Tfno: +34.91.312.99.72
Fax: +34.983.36.75.64
http://www.tid.es<http://www.tid.es/>


________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx


________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-jira/attachments/20130821/f74b952e/attachment.html>