Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CCP issue resolved for Okta Single Sign ON #11556

Merged
merged 3 commits into from
Dec 12, 2024
Merged

CCP issue resolved for Okta Single Sign ON #11556

merged 3 commits into from
Dec 12, 2024

Conversation

v-prasadboke
Copy link
Contributor

@v-prasadboke v-prasadboke commented Dec 12, 2024

Required items, please complete

Change(s):

  • Changed parameter name

Reason for Change(s):

  • CCP connector was not connecting due parameter name change
  • Maintemplate had parameters with same name 'Workspace'
  • Which were declared in global scope and local scope separately

Version Updated:

  • Yes to 3.1.1

Testing Completed:

  • image

@v-prasadboke v-prasadboke added Connector Connector specialty review needed Solution Solution specialty review needed labels Dec 12, 2024
@v-prasadboke v-prasadboke requested review from a team as code owners December 12, 2024 11:38
@v-prasadboke v-prasadboke changed the title CCP issue resolved CCP issue resolved for Okta Single Sign ON Dec 12, 2024
@v-atulyadav v-atulyadav merged commit c6c1afd into master Dec 12, 2024
48 checks passed
@its-sukhi
Copy link

its-sukhi commented Dec 18, 2024

Hey, Hope you are doing well!

I've just tried to connect one of our Okta repos to Sentinel through the CCP data connector and I'm getting this error:

"correlationId": "8d4661fc-53de-4ce0-9122-07a6cc423aaf", "description": "", "eventDataId": "dbd8dafa-7189-4dec-bbc4-a6f14535c57f", "eventName": { "value": "EndRequest", "localizedValue": "End request" }, "category": { "value": "Administrative", "localizedValue": "Administrative" }, "eventTimestamp": "2024-12-18T20:07:16.4020801Z", "id": "/subscriptions/xxx/resourcegroups/xxx/providers/Microsoft.Resources/deployments/DataConnector-OktaSSOv2Connections/events/dbd8dafa-7189-4dec-bbc4-a6f14535c57f/ticks/638701492364020801", "level": "Error", "operationId": "cfc84c10-a519-4589-bbb7-9ecdfb9b1dbe", "operationName": { "value": "Microsoft.Resources/deployments/write", "localizedValue": "Create Deployment" }, "resourceGroupName": "xxx", "resourceProviderName": { "value": "Microsoft.Resources", "localizedValue": "Microsoft Resources" }, "resourceType": { "value": "Microsoft.Resources/deployments", "localizedValue": "Microsoft.Resources/deployments" }, "resourceId": "/subscriptions/xxx/resourcegroups/xxx/providers/Microsoft.Resources/deployments/DataConnector-OktaSSOv2Connections", "status": { "value": "Failed", "localizedValue": "Failed" }, "subStatus": { "value": "BadRequest", "localizedValue": "Bad Request (HTTP Status Code: 400)" }, "submissionTimestamp": "2024-12-18T20:08:53Z", "subscriptionId": "xxx", "tenantId": "xxx", "properties": { "statusCode": "BadRequest", "serviceRequestId": null, "statusMessage": "{\"error\":{\"code\":\"InvalidTemplate\",\"message\":\"Deployment template validation failed: 'The template resource 'xxx/Microsoft.SecurityInsights/{{innerWorkspace}}/Microsoft.SecurityInsights/OktaDCV1_{{domainname}}' for type 'Microsoft.OperationalInsights/workspaces/providers/dataConnectors' at line '60' and column '85' has incorrect segment lengths. A nested resource type must have identical number of segments as its resource name. A root resource type must have segment length one greater than its resource name. Please see https://aka.ms/arm-syntax-resources for usage details.'.\",\"additionalInfo\":[{\"type\":\"TemplateViolation\",\"info\":{\"lineNumber\":60,\"linePosition\":85,\"path\":\"properties.template.resources[0].type\"}}]}}", "eventCategory": "Administrative", "entity": "/subscriptions/xxx/resourcegroups/xxx/providers/Microsoft.Resources/deployments/DataConnector-OktaSSOv2Connections", "message": "Microsoft.Resources/deployments/write", }, "relatedEvents": [] }

It seems like the request isn't making it to the Okta side from looking at the last used date/time for the API token. I've tested in two separate Azure accounts with two different Okta repos on each and it's giving me the same error each time.

Any help with this would be appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Connector Connector specialty review needed Solution Solution specialty review needed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants