Project

General

Profile

Actions

action #1729

closed

iChain integration

Added by ancorgs over 10 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Feature requests
Target version:
Start date:
2014-05-08
Due date:
% Done:

100%

Estimated time:
(Total: 5.00 h)

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 1 (0 open1 closed)

action #2458: better login handlingResolvedoholecek2014-05-08

Actions
Actions #1

Updated by alarrosa over 10 years ago

  • Target version changed from Sprint 03 to Sprint 04
Actions #2

Updated by ancorgs over 10 years ago

  • Priority changed from High to Urgent
Actions #3

Updated by alarrosa over 10 years ago

  • Target version deleted (Sprint 04)
Actions #4

Updated by lnussel over 10 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.

Actions #5

Updated by ancorgs over 10 years ago

  • Priority changed from Urgent to Normal
Actions #6

Updated by ancorgs over 10 years ago

  • Target version set to future
Actions #7

Updated by coolo almost 10 years ago

  • Assignee deleted (ancorgs)
Actions #8

Updated by coolo almost 10 years ago

  • Category set to 130
Actions #9

Updated by oholecek almost 10 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.

Actions #10

Updated by oholecek over 9 years ago

  • Status changed from In Progress to Resolved
Actions #11

Updated by okurz over 6 years ago

  • Target version changed from future to future
Actions

Also available in: Atom PDF