SAP Knowledge Base Article - Preview

3376134 - "XXXX BAD User is authenticated but not connected. " persists after security roles deployed


The below error still occurs after Security Artifact deployed and the security roles has been deployed according to SAP KBA 3083459 - "BAD User is authenticated but not connected." with Microsoft Office365-OAuth2 Authorization.
[CONTENT][CONTENT_DEPLOY][InstanceError] : {"message":"POLL_FAILED","parameters":["imaps://"],"childMessageInstances":[{"message":"EXCEPTION","parameters":["javax.mail.MessagingException: XXXX BAD User is authenticated but not connected."],"childMessageInstances":[{"message":"CAUSE","parameters":["com.sun.mail.iap.BadCommandException: XXXX BAD User is authenticated but not connected."]}]}]}



  • SAP Business Technology Platform
  • SAP Integration Suite
  • Cloud Integration


Cloud Integration all versions ; SAP Integration Suite all versions


Cloud Integration, Integration Suite, HCI, CPI, SCPI, HANA Cloud Integration, tenant, iFlow, Integration Flow, Mail adapter, OAuth, OAuth2, Office365 , KBA , LOD-HCI-PI-CON-SOAP , SOAP Adapter , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.