public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
To: Shannon Sterz <s.sterz@proxmox.com>
Cc: pbs-devel@lists.proxmox.com, pve-devel@lists.proxmox.com
Subject: Re: [PATCH proxmox-backup v4 23/24] notifications: Add OAuth2 section to SMTP target docs
Date: Fri, 24 Apr 2026 10:46:09 +0200	[thread overview]
Message-ID: <xm633j5mdlvypk7xppgtmsbdj2al6ujftxrrvbrklhlu2hfzgg@pgfklcxkbwym> (raw)
In-Reply-To: <DI18K9BI2DN8.Y5ETR5RY9WK3@proxmox.com>

On Fri, Apr 24, 2026 at 10:18:38AM +0200, Shannon Sterz wrote:
> On Fri Apr 24, 2026 at 9:59 AM CEST, Arthur Bied-Charreton wrote:
> > On Thu, Apr 23, 2026 at 02:24:30PM +0200, Shannon Sterz wrote:
> >> On Tue Apr 21, 2026 at 1:59 PM CEST, Arthur Bied-Charreton wrote:
> 
> -->8 snip 8<--
> 
> >> > +Google
> >> > +''''''
> >> > +
> >> > +Google does not allow bare IP addresses as redirect URIs. To work around this,
> >> > +add an entry to ``/etc/hosts`` **on the machine where your browser is
> >> > +running**, i.e., your local workstation.
> >> > +
> >> > +::
> >> > +
> >> > +    # Replace <IP> with the IP address of your Proxmox Backup Server node
> >> > +    <IP> local.oauth2-redirect.com
> >> > +
> >>
> >> not sure if that makes sense here. what if the device a user is using
> >> doesn't allow changing the hosts file (e.g. insufficient permissions or
> >> they are using a locked down phone etc.)?
> >>
> >> if we do add this section, consider using a reserved second level domain
> >> instead [1]. using a domain that could be be registered and misused
> >> seems dangerous to me.
> >>
> >> [1]: https://datatracker.ietf.org/doc/html/rfc2606#section-3
> >>
> > Thanks for the feedback! I am actually unsure if this hack even belongs
> > in our docs now that I think about it again. Maybe it would suffice to
> > just add a warning stating that Google does not allow bare IP addresses
> > and let users figure out how they want to work around that, or even
> > remove it altogether - what do you think? It is not really related to
> > PBS itself after all.
> >
> 
> yes adding a warning that bare ips aren't accepted and dropping the
> work-around section seems reasonable to me. we tend to target an
> audience that can probably figure out a work around if needed. so it
> shouldn't be to hard to come up with a way to make address resolution
> work on their end.
> 
> if you want to keep a hint at the host file around you could do
> something like this imo:
> 
> .. NOTE:: Google does not allow IP addresses as redirect URIs. If you
>    need to work around this, specify a dummy domain as the redirect URI
>    and make sure that your local machine resolves it to the proper IP
>    address (by, for example, adding a line to ``/etc/hosts``).
> 
> and leave it at that, most of our users should hopefully be able to
> figure out how to make this work for them.
> 
> -->8 snip 8<--
Sounds good, will do that - thank you for the review!




  reply	other threads:[~2026-04-24  8:46 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-21 11:59 [PATCH docs/manager/proxmox{,-perl-rs,-widget-toolkit,-backup} v4 00/24] fix #7238: Add XOAUTH2 authentication support for SMTP notification targets Arthur Bied-Charreton
2026-04-21 11:59 ` [PATCH proxmox v4 01/24] Add oauth2 and ureq to workspace dependencies Arthur Bied-Charreton
2026-04-21 11:59 ` [PATCH proxmox v4 02/24] notify: smtp: Introduce xoauth2 module Arthur Bied-Charreton
2026-04-21 11:59 ` [PATCH proxmox v4 03/24] notify: smtp: Introduce state management Arthur Bied-Charreton
2026-04-23 12:24   ` Shannon Sterz
2026-04-24  7:47     ` Arthur Bied-Charreton
2026-04-24  8:04       ` Shannon Sterz
2026-04-24  8:54         ` Arthur Bied-Charreton
2026-04-24  8:59           ` Shannon Sterz
2026-04-21 11:59 ` [PATCH proxmox v4 04/24] notify: smtp: Factor out transport building logic Arthur Bied-Charreton
2026-04-21 11:59 ` [PATCH proxmox v4 05/24] notify: smtp: Update API with OAuth2 parameters Arthur Bied-Charreton
2026-04-21 11:59 ` [PATCH proxmox v4 06/24] notify: smtp: Infer auth method for backwards compatibility Arthur Bied-Charreton
2026-04-21 11:59 ` [PATCH proxmox v4 07/24] notify: smtp: Add state handling logic Arthur Bied-Charreton
2026-04-23 12:24   ` Shannon Sterz
2026-04-24  7:50     ` Arthur Bied-Charreton
2026-04-21 11:59 ` [PATCH proxmox v4 08/24] notify: smtp: Add XOAUTH2 authentication support Arthur Bied-Charreton
2026-04-21 11:59 ` [PATCH proxmox-perl-rs v4 09/24] pve-rs: notify: smtp: add OAuth2 parameters to bindings Arthur Bied-Charreton
2026-04-21 11:59 ` [PATCH proxmox-perl-rs v4 10/24] pve-rs: notify: Add binding for triggering state refresh Arthur Bied-Charreton
2026-04-21 11:59 ` [PATCH proxmox-widget-toolkit v4 11/24] utils: Add OAuth2 flow handlers Arthur Bied-Charreton
2026-04-23 12:24   ` Shannon Sterz
2026-04-24  8:44     ` Arthur Bied-Charreton
2026-04-24  8:53       ` Shannon Sterz
2026-04-21 11:59 ` [PATCH proxmox-widget-toolkit v4 12/24] utils: oauth2: Add callback handler Arthur Bied-Charreton
2026-04-21 11:59 ` [PATCH proxmox-widget-toolkit v4 13/24] notifications: Add opt-in OAuth2 support for SMTP targets Arthur Bied-Charreton
2026-04-21 11:59 ` [PATCH pve-manager v4 14/24] notifications: smtp: api: Add XOAUTH2 parameters Arthur Bied-Charreton
2026-04-21 11:59 ` [PATCH pve-manager v4 15/24] notifications: Add trigger-state-refresh endpoint Arthur Bied-Charreton
2026-04-21 11:59 ` [PATCH pve-manager v4 16/24] notifications: Trigger notification target refresh in pveupdate Arthur Bied-Charreton
2026-04-21 11:59 ` [PATCH pve-manager v4 17/24] login: Handle OAuth2 callback Arthur Bied-Charreton
2026-04-21 11:59 ` [PATCH pve-manager v4 18/24] fix #7238: notifications: smtp: Add XOAUTH2 support Arthur Bied-Charreton
2026-04-21 11:59 ` [PATCH proxmox-backup v4 19/24] notifications: Add XOAUTH2 parameters to endpoints Arthur Bied-Charreton
2026-04-21 11:59 ` [PATCH proxmox-backup v4 20/24] login: Handle OAuth2 callback Arthur Bied-Charreton
2026-04-21 11:59 ` [PATCH proxmox-backup v4 21/24] fix #7238: notifications: smtp: Add XOAUTH2 support Arthur Bied-Charreton
2026-04-21 11:59 ` [PATCH proxmox-backup v4 22/24] daily-update: Refresh OAuth2 state for SMTP notification endpoints Arthur Bied-Charreton
2026-04-21 11:59 ` [PATCH proxmox-backup v4 23/24] notifications: Add OAuth2 section to SMTP target docs Arthur Bied-Charreton
2026-04-23 12:24   ` Shannon Sterz
2026-04-24  7:59     ` Arthur Bied-Charreton
2026-04-24  8:18       ` Shannon Sterz
2026-04-24  8:46         ` Arthur Bied-Charreton [this message]
2026-04-21 11:59 ` [PATCH pve-docs v4 24/24] notifications: Add OAuth2 section to SMTP targets docs Arthur Bied-Charreton

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=xm633j5mdlvypk7xppgtmsbdj2al6ujftxrrvbrklhlu2hfzgg@pgfklcxkbwym \
    --to=a.bied-charreton@proxmox.com \
    --cc=pbs-devel@lists.proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=s.sterz@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal