You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The Jira connector to Sentinel is not working as expected for Jira Datacenter. The REST API connector fails with 401 and 403 errors, and the Azure Function deployment also encounters connection issues, possibly due to an expectation of Jira Cloud instead of an on-premise installation as function error log proves.
To Reproduce
Configure the Jira connector to Sentinel.
Generate Personal Access Token from Jira Datacenter
Attempt to run connector against Jira Datacenter on-premise installation at https://enviroment.example.com
Alternatively deploy the Azure Function connector
See error: Connection issues and authentication errors.
For Jira Connector get: 401,403 errors in Connector page. Manually connecting using PAT credentials from windows terminal via endpoint connection is successful (proves that credentials are correct).
Deploying Azure Function will result following error:
2025-02-27T12:50:00Z [Error] Something wrong. Exception error text: HTTPSConnectionPool(host='enviroment.example.com.atlassian.net', port=443): Max retries exceeded with url: /rest/api/3/auditing/record?offset=0&limit=1000&from=2025-02-27T12%3A30%3A00Z&to=2025-02-27T12%3A40%3A00Z (Caused by SSLError(SSLCertVerificationError("hostname 'enviroment.example.com.atlassian.net' doesn't match either of '*.atlassian.net', 'atlassian.net'")))
Expected behavior
The Jira connector should successfully connect to Sentinel from Jira Datacenter environment, allowing queries to run and logs to be generated without authentication or connection issues.
Desktop (please complete the following information):
OS: Windows 11
Browser Chrome
Version Latest
The text was updated successfully, but these errors were encountered:
Describe the bug
The Jira connector to Sentinel is not working as expected for Jira Datacenter. The REST API connector fails with 401 and 403 errors, and the Azure Function deployment also encounters connection issues, possibly due to an expectation of Jira Cloud instead of an on-premise installation as function error log proves.
To Reproduce
Configure the Jira connector to Sentinel.
Generate Personal Access Token from Jira Datacenter
Attempt to run connector against Jira Datacenter on-premise installation at https://enviroment.example.com
Alternatively deploy the Azure Function connector
See error: Connection issues and authentication errors.
For Jira Connector get: 401,403 errors in Connector page. Manually connecting using PAT credentials from windows terminal via endpoint connection is successful (proves that credentials are correct).
Deploying Azure Function will result following error:
2025-02-27T12:50:00Z [Warning] Certificate did not match expected hostname: enviroment.example.com.atlassian.net. Certificate: {'subject': ((('countryName', 'US'),), (('stateOrProvinceName', 'California'),), (('localityName', 'San Francisco'),), (('organizationName', 'Atlassian US, Inc.'),), (('commonName', '.atlassian.net'),)), 'issuer': ((('countryName', 'US'),), (('organizationName', 'DigiCert Inc'),), (('commonName', 'DigiCert Global G2 TLS RSA SHA256 2020 CA1'),)), 'version': 3, 'serialNumber': '0DE4F9F4C912224E953E5424013E0843', 'notBefore': 'Nov 24 00:00:00 2024 GMT', 'notAfter': 'Dec 13 23:59:59 2025 GMT', 'subjectAltName': (('DNS', '.atlassian.net'), ('DNS', 'atlassian.net')), 'OCSP': ('http://ocsp.digicert.com',), 'caIssuers': ('http://cacerts.digicert.com/DigiCertGlobalG2TLSRSASHA2562020CA1-1.crt',), 'crlDistributionPoints': ('http://crl3.digicert.com/DigiCertGlobalG2TLSRSASHA2562020CA1-1.crl', 'http://crl4.digicert.com/DigiCertGlobalG2TLSRSASHA2562020CA1-1.crl')}
2025-02-27T12:50:00Z [Error] Something wrong. Exception error text: HTTPSConnectionPool(host='enviroment.example.com.atlassian.net', port=443): Max retries exceeded with url: /rest/api/3/auditing/record?offset=0&limit=1000&from=2025-02-27T12%3A30%3A00Z&to=2025-02-27T12%3A40%3A00Z (Caused by SSLError(SSLCertVerificationError("hostname 'enviroment.example.com.atlassian.net' doesn't match either of '*.atlassian.net', 'atlassian.net'")))
Expected behavior
The Jira connector should successfully connect to Sentinel from Jira Datacenter environment, allowing queries to run and logs to be generated without authentication or connection issues.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: