REST connector config

[asp]

Hi all,

When you go to configure a REST Connector, once you have set up the 'connectionJSON' and 'saved' the connection object, this field shows up hashed and not in clear text. It makes it difficult to identify issues, or triage if the connection parameters aren't correct. Is this the expected behavior? Is there a way to make the UI not hash this field, after it has been updated the first time?

[rushikeshvartak]

Confidential information should be masked. If you don’t need information to be masked then go to admin - identity Repository - connection - connection types - rest

remove connectionJSON from show encrypted values

this is not best practices

[sushmita]

Thanks for the info! Is there a special role to remove this field? Cannot do this for role_uiadmin and role_admin. I also checked the documentation but did not find anything.

https://saviynt.freshdesk.com/support/solutions/articles/43000541585-updating-connection-type

[rushikeshvartak]

This needs to be done from DB (Table name : externalconnectiontype)

Best practices - Enable REST Questionaries from Global Config -> Preference - Features

Rest Questionnaire

Do you want to enable self explained widget to configure Rest connector?

Output :

[asp]

I think we do have this enabled. But the issue is that we don't want the connectionJSON to be hashed. As that makes it incredibly cumbersome to triage connectivity issues or to make changes - much easier if we can see the JSON versus use the GUI and have the popup generate the json behind the scenes.

[asp]

I am not seeing this table in my Data Analyzer view (list of tables).

[rushikeshvartak]

Raise Saviynt Freshdesk ticket

[Manu269]

Try via analytics.

You should be able to view.

[rushikeshvartak · Accepted solution]

select ENCRYPTEDATTRIBUTES,CONNECTIONTYPE from externalconnectiontype where CONNECTIONTYPE='REST'

or

you can run query from custom query

update externalconnectiontype set ENCRYPTEDATTRIBUTES=null from where CONNECTIONTYPE='REST' limit 1;

[rushikeshvartak]

@asp  if above solution worked close the thread