This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
Following PR API is failing when we have < or > character in password . Can you enhance the password entry to accept all special character for password. Following are the more details.
PEM URL: https://apps.pem.ibmcloud.com/equifax/home?locale=en_US
PR URL: https://pr.pem.ibmcloud.com/equifax/login
PR API Request URL: https://pr.pem.ibmcloud.com:443/rest/sponsors/Equifax/usercredentials/
Request Method: POST
Request:
<?xml version="1.0" encoding="UTF-8"?>
<create username="EFAccess" password="76Pc729<" partner="d2551db5-b240-4d65-b18e-16469e7229a0"/>
Response:
<?xml version="1.0" encoding="UTF-8"?>
<error errorCode="400" errorDescription="Request is not valid XML."/>
API Response Status:
HTTP/1.1 400 Bad Request
Reason For Failure:
API execution failed:HTTP/1.1 400 Bad Request
What is your industry? | Financial Markets |
How will this idea be used?
With out this, Partners are not able to use password with special characters. |
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.
when i run the activity i get this error
API execution failed:HTTP/1.1 400 Bad Request
We have tried in the JSON format instead of XML still we are facing the same issue. Following is the response we have received.
We are going to work on this for a future consideration. In the iterim, can you try to submit this API request in a JSON format instead of XML? We believe that it should work in a JSON format while we consider addressing this for XML.
Hello Greg,
In this case passwords are partner remote profile password. In other words partner SFTP remote host passwords
Steven,
To clarify, the passwords that are being considered are passwords for access to SFG, correct?
Hi Greg,
Workaround you suggested would not work because we are trying to pass partner remote profile so cannot request customer to change his remote profile password.
Fyi - we are not able pass any XML characters in the password field in API.
So the request of this enhancement is accept all characters in the password field. Following is the API input.
<?xml version="1.0" encoding="UTF-8"?>
<create username="EFAccess" password="76Pc729<" partner="d2551db5-b240-4d65-b18e-16469e7229a0"/>
Please let me know if you have any questions.
Steven,
If I understand your request correctly, the limitation that you are seeing is that the special characters "<" and ">" can not be used. That does not preclude a whole list of other possible special characters that could be used, correct?
I will validate with the team, but my initial thought is that the < and > may be problematic when trying to pass these values in the XML delivered via API.
The workaround would be to add a regular expression to the password field to limit the special characters that can be used and provide a tool tip so that the users would be aware of what characters are allowed in a password.