Support Article

Connector Wizard fails when used Access Deny in Open instance

SA-5365

Summary

How to restrict access to Integration landing page.

Error Messages

Trying to evaluate Rule-Access-When conditions DenyMSDeveloperAccess when there is no page to evaluate them against

Steps to Reproduce

1. Create Rule Access Deny object. In 'Open Instances' provide a 'Access When' Rule in baseclass Condition.
2. Include the 'Rule Access Deny' in 'Rule Access Role' name and include it in 'Access Group'.
3. Try to initiate the connector Wizard by Integration->Connectors -> Connector and MetaData Wizard

Root Cause

@baseclass should not be referenced in Rule-Access-Deny rule, this is not a good practice and it will deny everything, even it will cause issue with logins and other key functionality. Creating Rule-Access-Deny at @baseclass level will give the above exception as no instance of anything is being opened.
Every landing page that has wizard, technically creates a work object (Work-). When Rule-Access-Deny returns Boolean “true” it denies the operation and grants access when Rule-Access-Deny returns Boolean “false”.

Resolution

1. Create new Access role name where Rule-Access-Deny is defined and assign it to Operator Access group.

2. Define the Rule-Access-Deny inside Access Role Name.

3. Create a Access Deny, inside which Rule-Access-When rule gets triggered during Open Instances.

4. Create Rule-Access-When rule, which defines conditions to deny opening of the application. In the example below, compare boolean true with true which should return true and Rule-Access-Deny should deny integration wizard.