Data Infrastructure Management Software Articles and Resources

Pre WFA 2.1 - Command and Workflow example for adding SSH publickey to a 7 mode system via API calls only

This DAR file contains a Workflow, Command, Dictionary Entry, and Template.  All of this is an example of adding a SSH publickey to an authorized_keys file on a 7 mode system.  This is done only with API calls, no NFS mounting of the root volume from a jumphost is necessary.

WFA doesn't seem to like long string entries, as I got the following error when trying to use a single variable for the full SSH key:

Data truncation: Data too long for column 'value' at row 1

As a workaround, I setup a template that chop's up the SSH key into 3 different variables, and the command then concatenates the key back into one piece.  Does anyone know if the issue noted above can be fixed in WFA?  It would be nice to enter it as a single variable, although not a big deal since I expect we will just setup a few templates for the small number of ONTAP users that need to have publickey authentication setup on a regular basis.

Please Note:

All content posted on the NetApp Community is publicly searchable and viewable. Participation in the NetApp Community is voluntary.

In accordance with our Code of Conduct and Community Terms of Use, DO NOT post or attach the following:

  • Software files (compressed or uncompressed)
  • Files that require an End User License Agreement (EULA)
  • Confidential information
  • Personal data you do not want publicly available
  • Another’s personally identifiable information (PII)
  • Copyrighted materials without the permission of the copyright owner

Continued non-compliance may result in NetApp Community account restrictions or termination.

Replies

Hi Mike,

>> WFA doesn't seem to like long string entries, as I got the following error when trying to use a single variable for the full SSH key:

>> Data truncation: Data too long for column 'value' at row 1

>> Does anyone know if the issue noted above can be fixed in WFA?

This has been fixed in the upcoming release of WFA which is 2.1 version.

Thanks,

Shailaja

WFA Team

All Community Forums