From: "Michael Honkoop" <MHonkoop@comsolve.nl>
To: <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] Feature: OAuth / OpenID-connect implementation
Date: Tue, 15 Dec 2020 00:12:10 +0100 [thread overview]
Message-ID: <5FD7F14A0200008800004144@mail.comsolve.nl> (raw)
In-Reply-To: <1607929849.0i4pachlbl.astroid@nora.none>
Hi Fabian,
Thanks for your hints regarding where to find the realm types,
researching further on my issue.
best regards,
Michael Honkoop
>>> Fabian Grünbichler <f.gruenbichler@proxmox.com> 8:12 14-12-2020
>>>
On December 13, 2020 2:16 am, Michael Honkoop wrote:
> Hi all,
>
> I am slowly working on implementing the authentication method/ entry
fields for it in PVE, which have shown up, and look to be fine (at
first glance).
>
> There are 2 things i am yes unable to grasp, and i hope you could
give me some directions :
>
> 1)
> UI :
> As Oauth/OpenID-connect does not have a need for a field 'tfa', but
its inherited from the common auth, i'd like to override it ( as in not
visible)
>
> 2)
> Schema:
> I cant seem to get where a/the schema is defined, or updated for that
matter.
> I mean i have the UI / auth on the dc level now showing an entry and
when i select add it will spawn the dialog to input parameters.
> However if i were to put some text in there and click add it spawns
an errormessage 'Parameter verification failed. (400)', 'type: value
'oauth' does not have a value in the enumeration 'ad, ldap, pam, pve''
and 'property is not defined in schema and the schema does not allow
additional properties'
>
> i've been searching where i can define it but this still have not
found, or better said due to my newness in this i'm not following where
it is/should be defined.
the possible realm types are defined here:
https://git.proxmox.com/?p=pve-access-control.git;a=blob;f=PVE/API2/Domains.pm;h=9c2b2548028790f19baaa81bde4cf0f071bb7719;hb=HEAD#l86
https://git.proxmox.com/?p=pve-access-control.git;a=blob;f=PVE/Auth/Plugin.pm;h=141305336c8640dd40879eb6e084b95c51ad0fa7;hb=HEAD
https://git.proxmox.com/?p=pve-access-control.git;a=tree;f=PVE/Auth;h=935646bae7647759c8b9ac04881275affb184500;hb=HEAD
each type registers as a plugin in the SectionConfig (which is in
pve-common), the add/update/delete schemas are generated from the
plugin
definitions.
>
> best regards,
>
> Michael Honkoop
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
>
>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2020-12-14 23:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-13 1:16 Michael Honkoop
2020-12-14 7:12 ` Fabian Grünbichler
2020-12-14 23:12 ` Michael Honkoop [this message]
2020-12-14 23:44 ` [pve-devel] Feature: OAuth / OpenID-connect implementation - II Michael Honkoop
2020-12-15 8:40 ` Fabian Grünbichler
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=5FD7F14A0200008800004144@mail.comsolve.nl \
--to=mhonkoop@comsolve.nl \
--cc=pve-devel@lists.proxmox.com \
/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