Routing Rule for Rejecting Unexpected Users - Teradata Unity

Teradata® Unity™ User Guide

Product
Teradata Unity
Release Number
16.50
Published
January 2020
Language
English (United States)
Last Update
2020-02-04
dita:mapPath
frp1571162435023.ditamap
dita:ditavalPath
ft:empty
dita:id
B035-2520
lifecycle
previous
Product Category
Analytical Ecosystem
It is a best practice to match an application or user to an appropriate use case and to determine who is allowed to connect to a production Unity environment. Use Unity reject routing rule assigned as the default rule in the user mappings when a user does not match any other user mapping.
unityadmin> routing update reject REJECT LOGON;
Successfully updated routing 'reject'