| |
Results |
|
SBM: OAuth2 tokens must be refreshed every hour
|
|
|
SBM: Setting up mailbox with OAuth2 prompts for admin consent
|
|
|
SBM: When setting up OAuth2 for Mail Server, refresh the Access Token gives error "Unknown error occurred. Please contact your Administrator"
|
|
|
Configuring OAuth2 with O365 for SBM Mail Services
|
On October 13th, 2020, Microsoft ended support for Basic authentication access for Office 365. In SBM 11.8, Micro Focus added support for OAuth 2 security with SBM Mail Servers using Office 365.
|
|
|
|
SBM Notification Server, Outlook 365 and OAuth 2.0
|
As of October 13, 2020, Office 365 will be discontinuing support for Basic Authentication to POP3, IMAP and Exchange Web Services. SMTP Auth will continue to use Basic Authentication on this date. What does this mean for SBM ?
|
|
|
|
Configuring OAuth 2 Security in SBM
|
- Returned by the service provider after successful authentication using Client ID and Client Secret (or Client Username / Client Password if Basic authentication is used instead). When the Access Token expires, SBM uses the Refresh Token to obtain a new access token. The following steps describe how to obtain these tokens using a utility that is provided by SBM.
|
|
|
|
MailClient throws ORA-00932 when using OAuth2.0
|
|
|
SBM: Notification suddenly stop being sent; incoming emails not being processed; error "Unable to obtain authentication details for Mailbox"
|
Notifications will suddenly stop sending emails, and incoming emails are no longer processed. This problem only impacts system which use OAuth 2 authentication for mailbox activity.
|
|
|
SBM Application Repository Guide
|
... ................................................... 57 Configuring OAuth 2 Security............................................ ...
|
|
|
|
SBM Application Repository Guide
|
... ................................................... 56 Configuring OAuth 2 Security............................................ ...
|
|
|
