Mailinglist Archive: opensuse-boosters (28 mails)
| < Previous | Next > |
Re: [opensuse-boosters] Topic for next meeting: OSUOSL
- From: Stephan Kulow <coolo@xxxxxxx>
- Date: Wed, 21 Sep 2011 10:53:39 +0200
- Message-id: <201109211053.39844.coolo@suse.de>
Am Mittwoch, 21. September 2011 schrieb Michal Hrusecky:
authenification can't stay behind login.opensuse.org if the real traffic is
then directly to the hoster.
We can then later switch from ldap auth to connect auth, but for now I
consider it a major regression if I need different accounts for different
openSUSE services.
Greetings, Stephan
--
To unsubscribe, e-mail: opensuse-boosters+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-boosters+help@xxxxxxxxxxxx
No, it's our own implementation.
What is login.opensuse.org and how it works? Strange question, but is it
documented somewhere? And isn't it just another iChain instance? AFAIK
Connect is behind some proxy that provides authentication which isconnect is behind login.opensuse.org, yes. And there is no reason why the
impossible (or at least hard) to do on servers hosted out of our
internal network. So if we are going to move some services out of Provo,
authenification can't stay behind login.opensuse.org if the real traffic is
then directly to the hoster.
We can then later switch from ldap auth to connect auth, but for now I
consider it a major regression if I need different accounts for different
openSUSE services.
Greetings, Stephan
--
To unsubscribe, e-mail: opensuse-boosters+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-boosters+help@xxxxxxxxxxxx
| < Previous | Next > |