IBM Sterling Ideas

Submit new product ideas for IBM Sterling solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed.

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

Connect with IBM experts and your peers on the Supply Chain Collaboration Community and the Order Management Interest Group

Better SSH Key matching functionality

Currently in order to perform SSH Key-based SFTP authentication for trading partners using SSP and SEAS we utilize the preconfigured "VerifySSHPublicKey" Attribute Assertion, defined as "{sshPublicKey_b64}" == "{attr[sshPublicKeyQuery].sshPublicKey}"

As a result, in order to perform any key-based validation of users, the user's public key must be manually trimmed to remove the key type and comments before storing it in LDAP. For example, the key
"ssh-rsa AAAAB3NzaC1yc2...qhsNLP user@server1" must be trimmed down to just "AAAAB3NzaC1yc2...qhsNLP"

We are attempting to implement more self-service functionality in configuring new interfaces, and as such we require users to submit their own requests to add SSH keys to their LDAP account. Users regularly forget to perform the manual trimming of keys, or do it incorrectly, requiring additional manual intervention to correct the key in LDAP.

Ideally SEAS should be able to recognize a valid key in either the OpenSSH or SSH2 format and correctly compare only the key-portion of the string to the actual key provided on login. Failing that, it should be possible to configure wildcards in the Attribute assertion definitions, or add a "contains" comparison operator, so that we could create an assertion that would match if the key in LDAP contains the key that is provided at login, without it being an exact match.
  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jan 8 2018
  • Delivered
What is the idea priority? High
DeveloperWorks ID DW_ID104721
Link to original RFE
  • Attach files
  • Admin
    VIJAY CHOUGULE commented
    9 Sep, 2019 08:40pm

    This issue has been addressed in SEAS ifix2 in Dec 2016. You should also be able to access this with latest SEAS ifix or SEAS GA.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    26 Aug, 2019 04:28pm

    The status now says delivered, is there any information regarding how it has been implemented (I offered a couple suggestions in my post) or what SEAS version is required?