We tried to create MP for Brocade switch. FOS REST API supports the XML (default) and JSON media types.
For the JSON media type, we have to include in the headers "application/yang-data+json". Unfortunately, Management Pack Builder does not support it and it include by default their media type "application/json" at the end of Accept.
Maybe somebody know any workaround for this, or how to force MPB to handle "application/yang-data+json" and not append application/json
Thank you for helping
Thanks for finding this issue. We were able to reproduce it and unfortunately we were not able to find a workaround. We will add support for custom Accept values (without appending application/json) in a future release of MP Builder.
Thank you for your answer
Do you know when next version of MPB will be available.
We are working on the 1.1 release now and plan on having it done as soon as possible, but we haven't announced a release date yet. We are going to try to add support for custom Accept headers in 1.1.
Hi, any news about new version of MPB. We need it to prepare MP for SAN switches monitoring.
Version 1.1 does have this feature in the scope. We are currently planning an April release date.
I'm using MPB 1.1.0 and I'm getting the same error "Unsupported Media Type" after login request to Brocade. Even if I specify "application/yang-data+json" as Content-Type and Accept label in the header, the Builder ignore them. I see following string in the log:
[DefaultDispatcher-worker-1] DEBUG ExecLogger  - -> Accept: application/json; application/yang-data+json; application/yang-data+json.
Any idea ?
We have a workaround which has led to success with other customers for FOS REST API:
1. In the Source, use basic authentication instead of session (we used running/brocade-chassis/chassis as the API Path, but you can use any working endpoint)
2. In the Source, set the Accept and Content-Type to "application/yang-data+json" (do not set Accept or Content-Type in individual requests)
Please let me know if this workaround works for you. If not, please provide screenshots of the Source and Request Accept header configurations.