Welcome to our community.

In this community, you can submit ideas, vote on existing ideas, or add comments.

To submit an idea, please click the Submit New Idea button at the top of the navigation sidebar. You will then be asked to add a title and choose a campaign for the new idea. You will also have the option to add tags to the idea. To vote on an idea, simply click the up or down arrows to the right of the idea title/description. And to add a comment, click in the box below the idea.

If you would like to see all ideas created with a specific tag, you can click on the word or phrase via the tagcloud in the navigation sidebar area under "What we're discussing". You can also view ideas sorted by Campaigns from the right navigation area. To return to this page, click the All Ideas link.

Validator

Set Association Status

It should be possible to set the association status of an associated object to test migration and sync events. Validating a status is already possible by checking “DirXML-Associations contain ‘Driver-DN#Assoc-Status#’”, migrating not associated objects by “Add DirXML-Associations ‘Driver-DN#4#’, but it’s not possible to change the status of an associated objects. Maybe, implementing Regexp + a replace feature could provide... more »

Voting

6 votes

Validator

Add Variable Indirection

Variable indirection allow another level of abstraction in using variables to modularize tests.

A simple example is to have a group of similarly name variables and the use of another variable to control the actual test values used. Example:

$StudentCN1="jstudent"
$StudentCX1="ou=students,o=school"
$StaffCN1="rstaff"
$StaffCX1="ou=staff,o=school"

You could define the test user, for one test pass by setting $Utype equal... more »

Voting

3 votes

Validator

Allow variables to be used in Connection field

Enabling a variable value to point to a connection, would allow easier development of modularity in templates and tests.

The use case I have involves multiple eDirectory connectors with in a single system. A variable change to the connection name in a common template would allow a single template to be used for similar tests in each of the different eDirectory trees.

Currently, the only way to achieve this easy reuse... more »

Voting

1 vote

Validator

Ability to Get/Convert CTIME and Set to Variable

It would be great to have an action that can get/convert CTIME and set to a variable. Ideally, this would mimic functionality of the Time noun and Convert Time verb that are supported by the engine. I realize you could accomplish this with scripts and the Execute connector, but it would be nice to have the functionality built-in to Validator.

Voting

3 votes

Validator

Disable Tests/actions by Connection

Hey Guys!
I'd like to be able to 'disable' actions for an entire connection - that would let me build integration tests (Say and HR JDBC driver to the Vault with AD and eDir drivers downstream) and run the same test suite as a Unit Test by disabling some connections (so I would disable the JDBC HR connection and eDir connections to unit test the AD driver - I would leave the connections to the ID Vault and AD domain active.... more »

Voting

2 votes

Validator

IDProvider Querying Capability

IDM has an 'ID Provider driver which generates unique IDs per one of a number of policies. It would be really nice if Validator had this option, perhaps as a connection option. The setup should be really simple for it to do. Accept an IP/DNS, port, policy ID, client ID (perhaps optional/random), and then store the retrieved ID in a variable for use later. The reason this would be nice is to allow testing of multiple... more »

Voting

0 votes

Validator

Change UserApp 'Approve Request' Labels

I was struggling to figure out why I could not approve a request with the UserApp connector. This was the error I would get: java.lang.AssertionError: java.lang.Exception: No task for this process/user while executing action method approveRequest. After using tcptunnel.sh to view the getWorkEntries SOAP call that Validator is making, it became apparent that the Recipient FDN is actually the addressee, and that the Process... more »

Voting

2 votes