Seaspray Error During Provisioning

Identity Security Cloud (ISC) ISC Discussion and Questions
, , ,
1

I am requesting access to a JDBC app. I have a provisioning rule set up, but I’m getting this error when requesting access:

An unexpected error occurred: Encountered “=” at seaspray[line 1, column 15] Was expecting one of: “[” … … … “-” … “+” … “*” … “/” … “%” … <LOGICAL_AND> … <LOGICAL_OR> … <LOGICAL_LT> … <LOGICAL_LE> … <LOGICAL_GT> … <LOGICAL_GE> … <LOGICAL_EQUALS> … <LOGICAL_NOT_EQUALS> …

I figured the error was coming from my rule so I removed the rule from my Source configuration. I re-requested the access and got the same error.

Does anyone have any insight into what the issue may be?

2

please check ccg logs and can you see what is the exact error

3

Seaspray typically refers to a transform in ISC, are there any transforms being used for this?

4

I don’t know of any Transforms being used. Where would I look? Would it be a Transform that is specific to the Source that I’m requesting for?

5

This is all that I see in the ccg.log:

“message”: “Provision Not Successful”,

“message”: “{\n "ccgLastMilePerformance" : {\n "opString" : "Create",\n "acctName" : "Vic Rinkenberger",\n "durationMsecs" : 680\n }\n}”,

6

can you see all the required are attributes are passing during create operation, have you configured provisioning policy?

7

This is the only attribute in the Create policy:

image
image617×208 6.04 KB

I’m not sure how to see if it is being passed correctly.

8

is that the only required attribute to create an account for jdbc?

9

Yes. Everything else is derived in the rule. I have attached the rule.

rule.java (12.9 KB)

10
  1. Identify the required account attributes to create an account in your target source
  2. Set static value for each attribute in Create Profile
  3. Test the provisioning and see whether it succeeded
  4. If it is success, then you can start build the logic on each account attributes.

This way, you can first easily identify the required attributes, and valid values for each attribute. Then you will get a clarity on what is expected in each attribute and what is the actual value you are getting on the logic, this leads you to debug the transforms or rules well.

To debug your error,

  1. Get the provisioning plan of this error (SailPoint Search > identity by name > Account Activity)
  2. Check each Account Activity event which includes the target source and inspect whether all the required attributes are included and populated with valid values
  3. Check in Create Profile for each attribute included in the provisioning plan and see whether it is using any transforms and debug it.
11

Thanks everyone. I found the issue. A transform in my Identity Profile was causing the error. Once I removed the transform, the error went away.

12

you can mark it as solution for this comment - Vincent KashatAmbassador