IBM Sterling Ideas

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

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.

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
1. Post an idea
2. Upvote ideas that matter most to you
3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

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.
  • Guest
  • Jan 8 2018
  • Delivered
DeveloperWorks ID DW_ID104721
Link to original RFE
  • 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.

  • 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? 

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.