From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id A73631FF141 for ; Tue, 05 May 2026 10:33:57 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id A85F21B3C9; Tue, 5 May 2026 10:33:36 +0200 (CEST) From: Arthur Bied-Charreton To: pve-devel@lists.proxmox.com, pbs-devel@lists.proxmox.com Subject: [PATCH proxmox-perl-rs v5 12/27] pve-rs: notify: add binding for initial OAuth2 refresh token exchange Date: Tue, 5 May 2026 10:32:33 +0200 Message-ID: <20260505083248.36450-13-a.bied-charreton@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260505083248.36450-1-a.bied-charreton@proxmox.com> References: <20260505083248.36450-1-a.bied-charreton@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.115 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_LAZY_DOMAIN_SECURITY 1 Sending domain does not have any anti-forgery methods RDNS_NONE 0.793 Delivered to internal network by a host with no rDNS SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_NONE 0.001 SPF: sender does not publish an SPF Record Message-ID-Hash: ZN2C7GAMF6VZTZJ32LWUKAHYHH473RCS X-Message-ID-Hash: ZN2C7GAMF6VZTZJ32LWUKAHYHH473RCS X-MailFrom: abied-charreton@jett.proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox Backup Server development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Expose the exchange_oauth2_code function from proxmox-notify's SMTP API. This will allow PVE to expose it as an endpoint, which is needed for the initial OAuth2 refresh token exchange that has to run in the backend. Signed-off-by: Arthur Bied-Charreton --- common/src/bindings/notify.rs | 25 ++++++++++++++++++++++++- 1 file changed, 24 insertions(+), 1 deletion(-) diff --git a/common/src/bindings/notify.rs b/common/src/bindings/notify.rs index 8316013..a0f79e4 100644 --- a/common/src/bindings/notify.rs +++ b/common/src/bindings/notify.rs @@ -26,7 +26,7 @@ pub mod proxmox_rs_notify { DeleteableSendmailProperty, SendmailConfig, SendmailConfigUpdater, }; use proxmox_notify::endpoints::smtp::{ - DeleteableSmtpProperty, SmtpConfig, SmtpConfigUpdater, SmtpPrivateConfig, + DeleteableSmtpProperty, SmtpAuthMethod, SmtpConfig, SmtpConfigUpdater, SmtpPrivateConfig, SmtpPrivateConfigUpdater, }; use proxmox_notify::endpoints::webhook::{ @@ -445,6 +445,29 @@ pub mod proxmox_rs_notify { ) } + /// Method: Exchange an OAuth2 authorization code for a refresh token. + /// + /// See [`api::smtp::exchange_oauth2_code`] + #[export(serialize_error)] + pub fn exchange_smtp_oauth2_code( + #[try_from_ref] _this: &NotificationConfig, + auth_method: SmtpAuthMethod, + client_id: String, + client_secret: String, + tenant_id: Option, + authorization_code: String, + redirect_uri: String, + ) -> Result { + api::smtp::exchange_oauth2_code( + auth_method, + client_id, + client_secret, + tenant_id, + authorization_code, + redirect_uri, + ) + } + /// Method: Delete an SMTP endpoint. /// /// See [`api::smtp::delete_endpoint`]. -- 2.47.3