action #1729

iChain integration

Added by ancorgs about 6 years ago. Updated almost 2 years ago.

Status:ResolvedStart date:08/05/2014
Priority:HighDue date:
Assignee:oholecek% Done:

100%

Category:Feature requestsEstimated time:5.00 hours
Target version:QA - future
Difficulty:
Duration:

Description

At some point, it will be useful to match the users in openQA DB with the users of the openSUSE infrastructure using iChain. Hopefully as a generic reusable plugin for Mojolicious.


Subtasks

action #2458: better login handlingResolvedoholecek

History

#1 Updated by alarrosa about 6 years ago

  • Target version changed from Sprint 03 to Sprint 04

#2 Updated by ancorgs about 6 years ago

  • Priority changed from High to Urgent

#3 Updated by alarrosa about 6 years ago

  • Target version deleted (Sprint 04)

#4 Updated by lnussel about 6 years ago

For deploying in opensuse infrastructure iChain is not necessarily required. We can put openqa behind the HA proxy which takes the https connection and forwards to mojo.

#5 Updated by ancorgs almost 6 years ago

  • Priority changed from Urgent to Normal

#6 Updated by ancorgs almost 6 years ago

  • Target version set to future

#7 Updated by coolo over 5 years ago

  • Assignee deleted (ancorgs)

#8 Updated by coolo over 5 years ago

  • Category set to 130

#9 Updated by oholecek about 5 years ago

  • Status changed from New to In Progress
  • Assignee set to oholecek

I want to convert Schema::Result::Users->openid to ->username field and during migration convert openid url to just usernames. That way switching openid<->iChain should be painless in our setups.

#10 Updated by oholecek about 5 years ago

  • Status changed from In Progress to Resolved

#11 Updated by okurz almost 2 years ago

  • Target version changed from future to future

Also available in: Atom PDF