starred/cypht

Fork 0

mirror of https://github.com/cypht-org/cypht.git synced 2026-04-25 04:56:03 +03:00

[GH-ISSUE #1463] 🐛 [Bug] Outlook oauth account invalid redirect url query #663

New issue

Open

opened 2026-02-25 21:35:37 +03:00 by kerem · 11 comments

kerem commented

2026-02-25 21:35:37 +03:00

Owner

Originally created by @WEGIII on GitHub (Mar 5, 2025).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/1463

Originally assigned to: @christer77, @Baraka24 on GitHub.

🐛 Bug

The redirect variable "http://localhost/?page=home" is not accepted in certain Azure app configs.
The Azure app redirect URL is not allowed to have a query in it unless the app is only for work or school accounts. See here: https://learn.microsoft.com/en-us/entra/identity-platform/reply-url.

I was able to complete the oauth GMAIL app setup as they took the queried redirect URL. I did modify the redirect URL to match my domain.

If I am misunderstanding this or there is a known fix, please advise. Thanks!

Version & Environment

Rev: cypht/cypht:2.4.0

OS: Docker Install

Originally created by @WEGIII on GitHub (Mar 5, 2025). Original GitHub issue: https://github.com/cypht-org/cypht/issues/1463 Originally assigned to: @christer77, @Baraka24 on GitHub.  ## 🐛 Bug  The redirect variable "http://localhost/?page=home" is not accepted in certain Azure app configs. The Azure app redirect URL is not allowed to have a query in it unless the app is only for work or school accounts. See here: https://learn.microsoft.com/en-us/entra/identity-platform/reply-url. I was able to complete the oauth GMAIL app setup as they took the queried redirect URL. I did modify the redirect URL to match my domain. If I am misunderstanding this or there is a known fix, please advise. Thanks! ### Version & Environment  Rev: cypht/cypht:2.4.0  OS: Docker Install

kerem added the

bug

label

2026-02-25 21:35:37 +03:00

kerem commented

2026-02-25 21:35:37 +03:00

Author

Owner

@christer77 commented on GitHub (Mar 13, 2025):

Hello @WEGIII ,

Thank you for this issue.

which messaging service are you trying with?
Gmail or Outlook or Office365 or..?

@christer77 commented on GitHub (Mar 13, 2025): Hello @WEGIII , Thank you for this issue. which messaging service are you trying with? Gmail or Outlook or Office365 or..?

kerem commented

2026-02-25 21:35:37 +03:00

Author

Owner

@christer77 commented on GitHub (Mar 13, 2025):

If is outlook oauth
set your client_id, client_secret and redirect_url(client_uri)
#aoutlook
OUTLOOK_CLIENT_ID=your client_id
OUTLOOK_CLIENT_SECRET=your client_secret
OUTLOOK_CLIENT_URI=http://localhost:8800/
OUTLOOK_AUTH_URI=https://login.live.com/oauth20_authorize.srf
OUTLOOK_TOKEN_URI=https://login.live.com/oauth20_token.srf
OUTLOOK_REFRESH_URI=https://login.live.com/oauth20_token.srf

@christer77 commented on GitHub (Mar 13, 2025): If is outlook oauth set your client_id, client_secret and redirect_url(client_uri) #aoutlook OUTLOOK_CLIENT_ID=your client_id OUTLOOK_CLIENT_SECRET=your client_secret OUTLOOK_CLIENT_URI=http://localhost:8800/ OUTLOOK_AUTH_URI=https://login.live.com/oauth20_authorize.srf OUTLOOK_TOKEN_URI=https://login.live.com/oauth20_token.srf OUTLOOK_REFRESH_URI=https://login.live.com/oauth20_token.srf

kerem commented

2026-02-25 21:35:37 +03:00

Author

Owner

@WEGIII commented on GitHub (Mar 13, 2025):

Outlook.com

It seems using the port made some type of progress, but is still not working. MS Azure accepted the port as part of the redirect URI.

When trying to add the email account via outlook using OUTLOOK_CLIENT_URI=http://localhost:8800/ connection is refused.
When trying to add the email account via outlook using OUTLOOK_CLIENT_URI=https://DOMAIN:8800/ connection times out.

Unfortunately, no errors in the container log, any ideas?

@WEGIII commented on GitHub (Mar 13, 2025): Outlook.com It seems using the port made some type of progress, but is still not working. MS Azure accepted the port as part of the redirect URI. When trying to add the email account via outlook using OUTLOOK_CLIENT_URI=http://localhost:8800/ connection is refused. When trying to add the email account via outlook using OUTLOOK_CLIENT_URI=https://DOMAIN:8800/ connection times out. Unfortunately, no errors in the container log, any ideas?

kerem commented

2026-02-25 21:35:37 +03:00

Author

Owner

@christer77 commented on GitHub (Mar 13, 2025):

Outlook.com

It seems using the port made some type of progress, but is still not working. MS Azure accepted the port as part of the redirect URI.

When trying to add the email account via outlook using OUTLOOK_CLIENT_URI=http://localhost:8800/ connection is refused. When trying to add the email account via outlook using OUTLOOK_CLIENT_URI=https://DOMAIN:8800/ connection times out.

Unfortunately, no errors in the container log, any ideas?

Use of the port? No, that's my way of accessing the CYPTH application in localhost. If your URL doesn't require the port to access it, you won't need to populate the port.

@christer77 commented on GitHub (Mar 13, 2025): > Outlook.com > > It seems using the port made some type of progress, but is still not working. MS Azure accepted the port as part of the redirect URI. > > When trying to add the email account via outlook using OUTLOOK_CLIENT_URI=http://localhost:8800/ connection is refused. When trying to add the email account via outlook using OUTLOOK_CLIENT_URI=https://DOMAIN:8800/ connection times out. > > Unfortunately, no errors in the container log, any ideas? Use of the port? No, that's my way of accessing the CYPTH application in localhost. If your URL doesn't require the port to access it, you won't need to populate the port.

kerem commented

2026-02-25 21:35:37 +03:00

Author

Owner

@WEGIII commented on GitHub (Mar 13, 2025):

I am able to access the application via domain or localhost. The concern is while trying to add the oauth redirect URI to the Azure app. In the screenshot below, Azure, this is where the redirect variable "http://localhost/?page=home" is not accepted due to it being a query string.

@WEGIII commented on GitHub (Mar 13, 2025): I am able to access the application via domain or localhost. The concern is while trying to add the oauth redirect URI to the Azure app. In the screenshot below, Azure, this is where the redirect variable "http://localhost/?page=home" is not accepted due to it being a query string. ![Image](https://github.com/user-attachments/assets/a80b6352-0495-4889-819b-5eba762c48b2)

kerem commented

2026-02-25 21:35:37 +03:00

Author

Owner

@christer77 commented on GitHub (Jun 24, 2025):

Hello @WEGIII

Can you test this

@christer77 commented on GitHub (Jun 24, 2025): Hello @WEGIII Can you test [this](https://www.cypht.org/cypht-enable-outlook-and-office365-oauth/)

kerem commented

2026-02-25 21:35:37 +03:00

Author

Owner

@Huiaei commented on GitHub (Aug 19, 2025):

1. App Password Login Issue

Authentication failed when attempting to log in via IMAP/SMTP protocol using an app password.

2. OAuth 2.0 Authentication Issues

Refer to the Cypht documentation (OAuth) and environment variable configuration methods for setup.

2.1. Initial Attempt and Error

During the first attempt at OAuth authorization redirection, the redirect_uri parameter in the link used was https://localhost/?page=home.
The following error message was received: invalid_request: The provided value for the input parameter 'redirect_uri' is not valid. The expected value is a URI which matches a redirect URI registered for this client application. (The redirect URI does not match what is registered for this client application.)

2.2. Azure AD Redirect URI Configuration Restriction

When configuring the redirect URI in the Azure portal, it was found that the URL does not allow query strings (e.g., ?page=home).

2.3. Successful Redirection in Local Environment

After removing the query string and changing the redirect_uri to https://localhost, the OAuth authorization process successfully redirected back.
The successfully returned URL was: https://localhost/?code=xxxxxxxxxxxxx&state=nux_authorization, indicating that the authorization code was received.

2.4. Error After Switching to Production Domain

Replacing localhost with the actual domain aaa.com in the successful link, i.e., https://aaa.com/?code=xxxxxxxxxxxxx&state=nux_authorization, resulted in an "An Error Occurred" message on the page.
Even attempting to revert the redirect_uri to https://aaa.com/?page=home (despite Azure AD not supporting query strings) also displayed "An Error Occurred".

Additional Note: Outlook SMTP Server Configuration

When configuring an Outlook mailbox, Cypht automatically populates the SMTP server address as smtp.office365.com.
According to official Microsoft documentation, the actual SMTP server for Outlook.com mailboxes should be smtp-mail.outlook.com.
Reference link: POP, IMAP, and SMTP settings for Outlook.com
It might be possible to manually enter the code and state values obtained from the localhost redirection (as described in 2.3) directly into Cypht to complete the authorization.
The Azure AD method appears overly cumbersome, especially since each Outlook account would require the creation of a separate application ID and secret, which is impractical for users with multiple accounts.

Thanks to Gemini for the translation and text reformatting, making it easier to understand.

@Huiaei commented on GitHub (Aug 19, 2025): **1. App Password Login Issue** * Authentication failed when attempting to log in via IMAP/SMTP protocol using an app password. **2. OAuth 2.0 Authentication Issues** Refer to the [Cypht documentation (OAuth)](https://www.cypht.org/cypht-enable-outlook-and-office365-oauth/) and environment variable configuration methods for setup. **2.1. Initial Attempt and Error** * During the first attempt at OAuth authorization redirection, the `redirect_uri` parameter in the link used was `https://localhost/?page=home`. * The following error message was received: `invalid_request: The provided value for the input parameter 'redirect_uri' is not valid. The expected value is a URI which matches a redirect URI registered for this client application.` (The redirect URI does not match what is registered for this client application.) **2.2. Azure AD Redirect URI Configuration Restriction** * When configuring the redirect URI in the Azure portal, it was found that the URL does not allow query strings (e.g., `?page=home`). **2.3. Successful Redirection in Local Environment** * After removing the query string and changing the `redirect_uri` to `https://localhost`, the OAuth authorization process successfully redirected back. * The successfully returned URL was: `https://localhost/?code=xxxxxxxxxxxxx&state=nux_authorization`, indicating that the authorization code was received. **2.4. Error After Switching to Production Domain** * Replacing `localhost` with the actual domain `aaa.com` in the successful link, i.e., `https://aaa.com/?code=xxxxxxxxxxxxx&state=nux_authorization`, resulted in an "An Error Occurred" message on the page. * Even attempting to revert the `redirect_uri` to `https://aaa.com/?page=home` (despite Azure AD not supporting query strings) also displayed "An Error Occurred". **Additional Note: Outlook SMTP Server Configuration** * When configuring an Outlook mailbox, Cypht automatically populates the SMTP server address as `smtp.office365.com`. * According to official Microsoft documentation, the actual SMTP server for Outlook.com mailboxes should be `smtp-mail.outlook.com`. * Reference link: [POP, IMAP, and SMTP settings for Outlook.com](https://support.microsoft.com/en-us/office/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) * It might be possible to manually enter the code and state values obtained from the localhost redirection (as described in 2.3) directly into Cypht to complete the authorization. * The Azure AD method appears overly cumbersome, especially since each Outlook account would require the creation of a separate application ID and secret, which is impractical for users with multiple accounts. --- Thanks to Gemini for the translation and text reformatting, making it easier to understand.

kerem commented

2026-02-25 21:35:37 +03:00

Author

Owner

@Huiaei commented on GitHub (Aug 19, 2025):

After reconfiguring from scratch, everything is now working correctly.

The deployment still follows the documentation to obtain the client_id and client_secret. The key steps involve modifying the redirect_url (i.e., client_uri) and the corresponding environment variables, and then adding the Outlook accounts.

Environment variable configuration is crucial:

OUTLOOK_CLIENT_ID=your_client_id
OUTLOOK_CLIENT_SECRET=your_client_secret
OUTLOOK_CLIENT_URI=your_web_link

Please note that OUTLOOK_CLIENT_URI and redirect_url must be set to the domain you use to access the Cypht service. For example, if you access your service via https://aaa.com, then both should be set to https://aaa.com.

Furthermore, different Outlook accounts can share the same client_id and client_secret, meaning there's no need to repeatedly configure and generate them for each account.

@Huiaei commented on GitHub (Aug 19, 2025): After reconfiguring from scratch, everything is now working correctly. The deployment still follows the [documentation](https://www.cypht.org/cypht-enable-outlook-and-office365-oauth/) to obtain the `client_id` and `client_secret`. The key steps involve modifying the `redirect_url` (i.e., `client_uri`) and the corresponding environment variables, and then adding the Outlook accounts. **Environment variable configuration is crucial:** ``` OUTLOOK_CLIENT_ID=your_client_id OUTLOOK_CLIENT_SECRET=your_client_secret OUTLOOK_CLIENT_URI=your_web_link ``` Please note that `OUTLOOK_CLIENT_URI` and `redirect_url` must be set to the domain you use to access the Cypht service. For example, if you access your service via `https://aaa.com`, then both should be set to `https://aaa.com`. Furthermore, different Outlook accounts can share the same `client_id` and `client_secret`, meaning there's no need to repeatedly configure and generate them for each account.

kerem commented

2026-02-25 21:35:37 +03:00

Author

Owner

@Huiaei commented on GitHub (Aug 19, 2025):

The Outlook SMTP authentication issue persists. Test results show either "Failed to authenticate to the SMTP server" or "Connected, but failed to authenticate to the SMTP server." Additionally, attempts to edit the relevant settings result in a save failure with the error "Authentication failed."

@Huiaei commented on GitHub (Aug 19, 2025): The Outlook SMTP authentication issue persists. Test results show either "Failed to authenticate to the SMTP server" or "Connected, but failed to authenticate to the SMTP server." Additionally, attempts to edit the relevant settings result in a save failure with the error "Authentication failed."

kerem commented

2026-02-25 21:35:37 +03:00

Author

Owner

@christer77 commented on GitHub (Aug 20, 2025):

The Outlook SMTP authentication issue persists. Test results show either "Failed to authenticate to the SMTP server" or "Connected, but failed to authenticate to the SMTP server." Additionally, attempts to edit the relevant settings result in a save failure with the error "Authentication failed."

Thank you @Huiaei for your feedback.

I am trying to reproduce your issue by reinstalling my entire environment.

I will get back to you shortly.

@christer77 commented on GitHub (Aug 20, 2025): > The Outlook SMTP authentication issue persists. Test results show either "Failed to authenticate to the SMTP server" or "Connected, but failed to authenticate to the SMTP server." Additionally, attempts to edit the relevant settings result in a save failure with the error "Authentication failed." Thank you @Huiaei for your feedback. I am trying to reproduce your issue by reinstalling my entire environment. I will get back to you shortly.

kerem commented

2026-02-25 21:35:37 +03:00

Author

Owner

@marclaporte commented on GitHub (Jan 28, 2026):

@marclaporte commented on GitHub (Jan 28, 2026): Related: https://github.com/cypht-org/cypht/issues/1846

kerem referenced this issue

2026-02-25 21:36:48 +03:00

[PR #663] [MERGED] Add search in sent mail throughout all accounts #966