Migrating of web resources to SSL

Discussion created by Daryl Herzmann

on Apr 16, 2014
Latest reply on Jun 9, 2014 by Daryl Herzmann

Like • Show 0 Likes0
Comment • 20

Hi all,

I would like to proceed with migrating our igniterealtime web resources to SSL protected. Jive will kindly purchase a cert for this effort. The most noticable change will be changes in URIs, like so:

http://issues.igniterealtime.org -> https://igniterealtime.org/issues/

http://bamboo.igniterealtime.org -> https://igniterealtime.org/bamboo/

...etc...

Of course, apache rewrite rules will be in place to make this 'transparent' and hopefully keep all links working going forward.

Anybody have concerns about this?

daryl

Outcomes

20 Replies

benjamin Apr 16, 2014 11:46 AM
Just a comment... I'm personally OK if the main website remains available via HTTP and we add HTTPS to it, so it would be available at both http or https. All the other resources (issues, bamboo, etc) would be secure as Daryl shows.

community.igniterealtime.org will NOT relocate to igniterealtime/community as I'm slowly but surely taking the steps needed to migrate it to the newere Jive Cloud platform.
Like • Show 0 Likes0
Actions
- SnakeDoc @ benjamin on Apr 16, 2014 11:53 AM
  is there a downside to serving everything over SSL?
  Like • Show 0 Likes0
  Actions
  - benjamin @ SnakeDoc on Apr 16, 2014 12:31 PM
    No big downsides I can think of, except that there's no need for it on a anonymous, read-only website.
    Like • Show 0 Likes0
    Actions
    - SnakeDoc @ benjamin on Apr 16, 2014 12:47 PM
      well, i guess one could argue the forums aren't anonymous and should be protected. at a glance, it appears the login for the forums is also being done over plain http.
      Like • Show 0 Likes0
      Actions
      - benjamin @ SnakeDoc on Apr 16, 2014 1:02 PM
        We will be securing the forums as well, just not relocating the resource from community.ignite -> ignite/community.
        Like • Show 0 Likes0
        Actions
Tom Evans Apr 16, 2014 12:30 PM
+1
Like • Show 0 Likes0
Actions
LG Apr 17, 2014 11:47 AM
community.igniterealtime.org: robots.txt only for ssl should be created and disallow indexing content.

PS: Don't do it, with OpenSSL we might be affected by Heartbleed. Plaintext login seems to be more secure
Like • Show 1 Like1
Actions
benjamin May 7, 2014 2:48 PM
Good news!

https://community.igniterealtime.org is now SSL ( you may have noticed ).

https://igniterealtime.org/ is now SSL enabled, too. Daryl is working on moving other service to sub URI's.
Like • Show 0 Likes0
Actions
- Daryl Herzmann @ benjamin on May 7, 2014 9:25 PM
  https://igniterealtime.org/issues/ should now be working. Please let me know of any troubles, old URLs should automagically be forwarded...
  Like • Show 0 Likes0
  Actions
  - LG @ Daryl Herzmann on May 7, 2014 10:07 PM
    https://community.igniterealtime.org/robots.txt and https://community.igniterealtime.org/sitemap/sitemap.xml do no longer exist. I'll look at it on Friday unless you have an idea how to fix it.
    Like • Show 0 Likes0
    Actions
    - benjamin @ LG on May 8, 2014 12:49 AM
      Fixed... though, I'm not sure if we get to keep these custom files in the new environment.
      Like • Show 0 Likes0
      Actions
  - wroot @ Daryl Herzmann on May 9, 2014 11:18 AM
    Daryl Herzmann wrote:
    
    https://igniterealtime.org/issues/ should now be working. Please let me know of any troubles, old URLs should automagically be forwarded...
    
    JIRA linking is not working anymore. I have tried putting the new main URL here https://community.igniterealtime.org/admin/edit-render-filter!input.jspa?filterN ame=JIRAFilter
    
    But it does nothing. Or maybe it needs time to propagate.
    Like • Show 0 Likes0
    Actions
    - wroot @ wroot on May 14, 2014 2:38 AM
      Also Bamboo has problems with automatic builds.
      Like • Show 0 Likes0
      Actions
Tom Evans May 8, 2014 10:32 AM
Heads-up ... looks like we have an issue with the new SSL certificate for community.igniterealtime.org: https://community.igniterealtime.org/message/239053#239053
Like • Show 0 Likes0
Actions
wroot May 25, 2014 2:07 AM
I see that JIRA links are now work in the forums. But i see error in JIRA:

Couldn't read data from Ignite Realtime Bamboo. Learn about this issue or go to application links to fix it.
Like • Show 0 Likes0
Actions
- Daryl Herzmann @ wroot on May 26, 2014 5:08 AM
  I think I have refreshed the config and it is okay now?
  Like • Show 0 Likes0
  Actions
  - wroot @ Daryl Herzmann on May 26, 2014 5:48 AM
    Still see the same error here OF-709
    Like • Show 0 Likes0
    Actions
    - Daryl Herzmann @ wroot on May 26, 2014 9:22 AM
      I have raised this issue with Contegix for their help.
      Like • Show 0 Likes0
      Actions
      - wroot @ Daryl Herzmann on Jun 6, 2014 11:43 AM
        Ok. I now see builds. But just numbers. If i click on it, it asks to authenticate, but it never does. I have a user in Bamboo (i think it's the same from JIRa, linked with Bamboo).
        
        But i still see error instead of commits info. It asks me to authenticate with Fisheye when i go to dashboard and i don't have a user in Fisheye. Maybe that's the cause of this error. Though it was at least showing number of commits before.
        Like • Show 0 Likes0
        Actions
        Daryl Herzmann @ wroot on Jun 9, 2014 11:10 AM
        Contegix is looking into this issue again.
        Like • Show 0 Likes0
        Actions

Migrating of web resources to SSL

Outcomes

Related Content

Recommended Content