Thursday, March 29, 2018

Servicenow Tables

<<table_name>>.list

sys_user_group --> Assignment groups
sys_user -- User list
sys_user_role -- User roles
sys_ui_policy --> UI Policy
sys_ui_policy_Action --> UI Policy Action
sys_scope  --> Will have list of scoped application details
sys_schema_attribute_m2m
sys_properties --> Have the System properties stored
sys_ui_form --> To view all the views related to a table 

wf_workflow  --> Master records of workflow
incident       --> contains incident list
dl_matcher  --> for lookup matcher

sc_req_item --> requested item list
sc_request   --> contain Request list

sc_cart   --> Shopping cart
sc_cart_item --> Item
sc_cat_item_guide_items --> Rule
sc_cat_item_guide --> Order guide
sc_catalog --> Catalog
sc_category --> Category
sc_cat_item --> Catalog item
sc_cat_item_producer --> Record Producer
sc_cat_item --> Catalog item



cmdb_model

For Assessment we have 25 Out of box tables
Metric Category   --> asmt_metric_category
Assessment Metric  --> asmt_metric
Assessment Metric Definition -- > asmt_metric_definition
Metric Result --> asmt_metric_result



core_company



We have same label name for different table names 

Wednesday, March 14, 2018

LDAP

https://stackoverflow.com/questions/18756688/what-are-cn-ou-dc-in-an-ldap-search

http://www.rlmueller.net/LDAP_Binding.htm



I have a search query in LDAP like this. What exactly does this query mean?
("CN=Dev-India,OU=Distribution Groups,DC=gp,DC=gl,DC=google,DC=com");

What are CN, OU, DC?
String  X.500 AttributeType
------------------------------
CN      commonName
L       localityName
ST      stateOrProvinceName
O       organizationName
OU      organizationalUnitName
C       countryName
STREET  streetAddress
DC      domainComponent
UID     userid

What does the string from that query mean?
The string ("CN=Dev-India,OU=Distribution Groups,DC=gp,DC=gl,DC=google,DC=com") is a path from an hierarchical structure (DIT = Directory Information Tree) and should be read from right (root) to left (leaf).
It is a DN (Distinguished Name) (a series of comma-separated key/value pairs used to identify entries uniquely in the directory hierarchy). The DN is actually the entry's fully qualified name.
Here you can see an example where I added some more possible entries.
The actual path is represented using green.
enter image description here
The following paths represent DNs (and their value depends on what you want to get after the query is run):
  • "DC=gp,DC=gl,DC=google,DC=com"
  • "OU=Distribution Groups,DC=gp,DC=gl,DC=google,DC=com"
  • "OU=People,DC=gp,DC=gl,DC=google,DC=com"
  • "OU=Groups,DC=gp,DC=gl,DC=google,DC=com"
  • "CN=QA-USA,OU=Distribution Groups,DC=gp,DC=gl,DC=google,DC=com"
  • "CN=Dev-India,OU=Distribution Groups,DC=gp,DC=gl,DC=google,DC=com"
  • "CN=Ted Owen,OU=People,DC=gp,DC=gl,DC=google,DC=com"


Second response


  • CN = Common Name
  • OU = Organizational Unit
  • DC = Domain Component
These are all parts of the X.500 Directory Specification, which defines nodes in a LDAP directory.
You can also read up on LDAP data Interchange Format (LDIF), which is an alternate format.
You read it from right to left, the right-most component is the root of the tree, and the left most component is the node (or leaf) you want to reach.
Each = pair is a search criteria.
With your example query
("CN=Dev-India,OU=Distribution Groups,DC=gp,DC=gl,DC=google,DC=com");
In effect the query is:
From the com Domain Component, find the google Domain Component, and then inside it the glDomain Component and then inside it the gp Domain Component.
In the gp Domain Component, find the Organizational Unit called Distribution Groups and then find the the object that has a common name of Dev-India.