Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

Starting Sessions

  1. Login to Yarngate

  2. Click +Prepare session(s)

  3. Add the systems that you would like access to and click +Prepare session

  4. Enter the required details for the session including password

  5. Review the sessions created

  6. Session details

  7. Session can then be closed

Starting SSH Session

  1. Click SSH Session and create session

  2. Select the system

  3. Access is granted

Entitlement review

This provides a view of all systems that the user has access to

Off-boarding

Offboarding provides a way to quickly remove all access for a user

  1. Create offboard task

  2. Search for user and add sessions

  3. Start off-board request

Reporting

New Sessions

Provide a list of all sessions created within yarngate and current status

System Access Snapshot

Create System Access Snapshot
  • Report type

    • Local yarngate, Queries the Yarngate database only

    • Local Yarngate+remote System, Queries the remote system for current configured information (WIP)

  • Filters

    • Username

    • App Profile

    • Customer

    • Cluster

    • Interfaces

    • Time Range

Limited to 30 results

Admin users

Create an Admin Users Report
  • Report interface selector(s)

    • Customer

    • Cluster

    • Entitlement group

    • Interface

Audit Log

Create an Audit Log Report
  • Select Elastic Search Interface and Index database

    • this is usually set to _all

  • Report interface selector(s)

    • Customer

    • Cluster

    • Entitlement group

    • Interface

    • manually add node(s)

      • Show all available nodes will provide a list of unique NodeIDs from the database that can be copied in the target node field

Configure Report objectives

  • Enter in username(s) or select an App profile to populate the user prefix.

  • Configuration changes Toggle provides a summary of changes made to the system(s)

  • Access Control Group is used to query enduser or applicationuser that has been manually added to the default cucm admin group via ccmadmin interface

  • Field Names - Depending on the database, subfields may need to be specified to prevent wrong tokenisation field data

  • No labels