WORKLOAD AUTOMATION COMMUNITY
  • Home
  • Blogs
  • Forum
  • Resources
  • Events
    • IWA 9.5 Roadshows
  • About
  • Contact
  • What's new

What's new in the Workload Automation portfolio.

We're always working on building new features and improving existing ones.
Here's where you can learn about all of our changes.

Enhancing authentication using API Keys

12/12/2022

 
10.1.0.1
DWC
Engine
On Premise

​Use API Keys to authenticate a command line or application easily and quickly.

You can create both Personal and Service API Keys in the Dynamic Workload Console and easily assign them to either specific users or groups. A comprehensive API Keys monitoring tool gives you full control over every valid, expiring and expired API Key that have been associated with an engine. For more information, see Authenticating the command line client using API Keys topic in the Documentation.

You can use API Keys to authenticate the command line. You can use an API Key to get authenticated when you launch composer, conman, wappman, and ocli commands, instead of having to provide username and password as in previous versions.

To use the API Key with these commands, you need to have a specific set of authorizations defined in the security file, so that you can generate and retrieve the key from the Dynamic Workload Console. To find out the required authorizations, see Object type - file topic in the Documentation.

To generate the key from the Dynamic Workload Console, perform the steps listed in Authenticating the command line client using API Keys.

After generating the token, you can either specify it in the command line with the -jwt parameter, or add it in the useropts file.

For more information about adding JWT in the useropts file, see Setting user options topic in the Documentation.

For more information about using JWT with commands, see Running the composer program, Running the conman program, wappman command.

You can also use the API Key to authenticate the master domain manager when installing the agents. This authentication allows the product to download the JWT or the certificates to be used for secure communication between master domain manager and dynamic agents. If you provide the API Key (with the apikey parameter), you no longer need to specify username and password (wauser and wapassword parameters) as in previous versions.

For more information about using the API Key for authentication purposes, see Agent installation parameters - twsinst script, Certificates download to dynamic agents - AgentCertificateDownloader script and Example installation commands topics in the Documentation.

Ensure there are no misalignments in date and time in your network nor significant network delays because this might impact JWT performance.

    Categories

    All
    10.1.0
    10.1.0.1
    9.5.0
    9.5.0.1
    9.5.0.2
    9.5.0.3
    9.5.0.4
    9.5.0.5
    API Keys
    Dwc
    Engine
    JWT
    Mainframe
    OCLI
    On-cloud
    On-cloud
    On Premise
    On-premise
    Orchestration CLI
    REST API
    SAAS
    Self-Service Catalog
    SSC

www.hcltechsw.com
About HCL Software 
HCL Software is a division of HCL Technologies (HCL) that operates its primary software business. It develops, markets, sells, and supports over 20 product families in the areas of DevSecOps, Automation, Digital Solutions, Data Management, Marketing and Commerce, and Mainframes. HCL Software has offices and labs around the world to serve thousands of customers. Its mission is to drive ultimate customer success with their IT investments through relentless innovation of its products. For more information, To know more  please visit www.hcltechsw.com.  Copyright © 2019 HCL Technologies Limited
  • Home
  • Blogs
  • Forum
  • Resources
  • Events
    • IWA 9.5 Roadshows
  • About
  • Contact
  • What's new