-
Bug
-
Resolution: Not a bug
-
Low
-
None
-
4.14.0, 4.13.1
-
None
-
Severity 3 - Minor
-
Issue Summary
Users cannot use OAuth 2.0 to configure shared mailboxes for Microsoft outlook office 365 since the custom settings do not currently support OAuth. JSM therefore uses the same email address as the username when authenticating, meaning you cannot provide the user who has been granted access to login.
Steps to Reproduce
Try to connect JSM to a Microsoft shared mailbox - you will not be able to provide the username causing the connection to fail
Expected Results
Ability to provide different username and email address to allow successful connection.
Actual Results
Exception will be thrown trying to connect...
Workaround
Customers can connect using basic auth and POP currently. Currently there is no known workaround for this behavior with OAuth 2.0. A workaround will be added here when available
[JSDSERVER-7057] Support for Microsoft Office 365 shared mailboxes in JSM using OAuth 2.0
| Resolution | New: Not a bug [ 12 ] | |
| Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
| Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
| Component/s | New: Email - Incoming [ 32490 ] | |
| Component/s | Original: Email - Incoming [ 46704 ] | |
| Key |
Original:
|
New:
|
| Symptom Severity | Original: Severity 3 - Minor [ 14432 ] | New: Severity 3 - Minor [ 15832 ] |
| Affects Version/s | New: 4.13.1 [ 92694 ] | |
| Affects Version/s | New: 4.14.0 [ 92890 ] | |
| Project | Original: Jira Service Management Cloud [ 18512 ] | New: Jira Service Desk Server and Data Center [ 15611 ] |