Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]Unable to set UCS as the4 source VIA API Call to /sessions/{session_id}/source #120

Open
c003466 opened this issue Dec 8, 2023 · 0 comments

Comments

@c003466
Copy link

c003466 commented Dec 8, 2023

Describe the bug
Unable to set UCS as the4 source VIA API Call to /sessions/{session_id}/source

Returns the following error irrespective of the body format I use

{
"detail": {
"all": [
"Either ucs_file or credentials has to be passed"
]
},
"status_code": 400
}

Other API endpoints work just fine. This functionality works in the GUI

To Reproduce
Steps to reproduce the behavior:

  1. using Postman to test
    url = "https://10.33.199.99/sessions/4/source"

payload = 'ucs_file=test.ucs&ucs_passphrase=abcde&as3_file=&username=&password=&host=&master_key=clsFC8lO0YDnwzeM5KkvmQ%3D%3D'
headers = {
'Content-Type': 'application/x-www-form-urlencoded'
}
3. but returns error whatever I put in the ucs_file field. Really I am just looking for an example of how to use this enpoint. I can not find example in Swagger Docs or on the Web. Reached out to dev central and F5 TAC but they pointed me here
4. See error

Expected behavior
I expect to get a 200 response rather than the 400 bad request I get at present

Screenshots
image

Context

  • Please specify, app version:

  • Latest version of Journeys tool from here

  • And Platform version of the system you want to migrate.

  • looking to migrate on prem F5 LTM to Azure DR LTM, currently running version 16.1.4.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant