From: "Lukáš Karas" <lukas.karas@centrum.cz>
To: Daniel Wagner <wagi@monom.org>
Cc: connman@lists.linux.dev,
Santtu Lakkala <santtu.lakkala@jolla.com>,
Jussi Laakkonen <jussi.laakkonen@jolla.com>
Subject: Re: Re: [PATCH] make possible to use alternative auth group with 2nd password
Date: Mon, 30 Aug 2021 08:52:01 +0200 [thread overview]
Message-ID: <15534700.KoKU9GZOxT@latitudemachine> (raw)
In-Reply-To: <20210805061457.abhvax5ow55z4hwt@beryllium.lan>
[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]
Hello guys.
Did you find some time to look at this patch? It would be great to support
openconnect with second factor authentication and alternative groups.
Btw, if I understand the code, connman form API doesn't support updating
of form fields dynamically right? (After change of openconnect group)
Lukas
Dne čtvrtek 5. srpna 2021 8:14:57 CEST Daniel Wagner napsal(a):
> Hi Lukas,
>
> On Wed, Aug 04, 2021 at 06:39:39PM +0200, Lukáš Karas wrote:
> > Some servers are configured with multiple authentication groups.
> > OpenConnect request just authentication entries that are valid
> > for specific group (process_auth_form method). So, authentication
> > group have to setup first, and new form have to be requested then.
> >
> > Some authentication groups may require secondary password.
> > For example one-time password from Google Authenticator app.
>
> From my quick glance it looks reasonable.
>
> @Santtu, as you have done some serious work recently on the plugin, do
> have any objections?
>
> Daniel
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-08-30 6:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 16:39 [PATCH] make possible to use alternative auth group with 2nd password Lukáš Karas
2021-08-05 6:14 ` Daniel Wagner
2021-08-30 6:52 ` Lukáš Karas [this message]
2021-08-30 8:16 ` Daniel Wagner
2021-08-30 17:37 ` Daniel Wagner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15534700.KoKU9GZOxT@latitudemachine \
--to=lukas.karas@centrum.cz \
--cc=connman@lists.linux.dev \
--cc=jussi.laakkonen@jolla.com \
--cc=santtu.lakkala@jolla.com \
--cc=wagi@monom.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).