Subscribing is a smart move!
You can subscribe to this forum after you log in or create your free account.
SOAPUI Authentication
SmartConnector Forum
Schneider Electric support forum about SmartConnector applications for integration of other building management systems (BMS) into EcoStruxure Building Operation.
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
Solved
Go to Solution
Link copied. Please paste this link to share this article on your social media post.
Accepted Solutions
Link copied. Please paste this link to share this article on your social media post.
Petri,
Glad to hear you are making progress. The Swagger metadata feed allows a large ecosystem of code generators to create clients stubs and proxys. We provide a .NET sample which based on this. You can find that in the samples repository in GitHub here: https://github.com/BuildingsLabs/SmartConnectorSamples.
As to your questions on how SoapUI needs to handle the Bearer token. Well, it needs to handle it like any HTTP client would; it needs to include an Authorization header with the value 'Bearer <value of the token> which was obtained from the token endpoint.
Here's an example. I'm using a slightly older version of SoapUI (v5.2.1) so my screen shots might be different.
- Create a "REST Project" with the URL of the base route e.g. http://localhost:8083.
- Obtain a token by issuing a "POST" to the token endpoint as shown here (/GetToken by default but that's configurable in your Endpoint Configuration in SmartConnector).
Note that the body contains the User Name and Password in the format:
grant_type=password&username=USERNAMEVALUE&password=PASSWORDVALUE
3. Grab the value of the Bearer Token from the response and add a Header value for another request. I'm showing "Root" since it's the simplest. The value of the header must be in the format Authorization = Bearer <TOKEN_VALUE> as shown here:
You can exercise any of the other actions similarly passing query and/or body parameters as needed but you'll always need to include the Authorization header. Remember, the Token does expire so you'll need to get an updated value when it does. You can adjust the token expiration in your Endpoint Configuration in SmartConnector but the maximum is 60 minutes. Default is 5 minutes.
Also, don't forget to double URL encode all query parameters. Body parameters don't need to be encoded like that but they do need to be in the proper format based on whatever your request format is.
Link copied. Please paste this link to share this article on your social media post.
Petri,
Glad to hear you are making progress. The Swagger metadata feed allows a large ecosystem of code generators to create clients stubs and proxys. We provide a .NET sample which based on this. You can find that in the samples repository in GitHub here: https://github.com/BuildingsLabs/SmartConnectorSamples.
As to your questions on how SoapUI needs to handle the Bearer token. Well, it needs to handle it like any HTTP client would; it needs to include an Authorization header with the value 'Bearer <value of the token> which was obtained from the token endpoint.
Here's an example. I'm using a slightly older version of SoapUI (v5.2.1) so my screen shots might be different.
- Create a "REST Project" with the URL of the base route e.g. http://localhost:8083.
- Obtain a token by issuing a "POST" to the token endpoint as shown here (/GetToken by default but that's configurable in your Endpoint Configuration in SmartConnector).
Note that the body contains the User Name and Password in the format:
grant_type=password&username=USERNAMEVALUE&password=PASSWORDVALUE
3. Grab the value of the Bearer Token from the response and add a Header value for another request. I'm showing "Root" since it's the simplest. The value of the header must be in the format Authorization = Bearer <TOKEN_VALUE> as shown here:
You can exercise any of the other actions similarly passing query and/or body parameters as needed but you'll always need to include the Authorization header. Remember, the Token does expire so you'll need to get an updated value when it does. You can adjust the token expiration in your Endpoint Configuration in SmartConnector but the maximum is 60 minutes. Default is 5 minutes.
Also, don't forget to double URL encode all query parameters. Body parameters don't need to be encoded like that but they do need to be in the proper format based on whatever your request format is.
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Hi Mark,
I also met the SOAP UI problem, Follow the step above, I got a message: {"error": "unsupported_grant_type"}, and I attached the capture picture here. Do you know anything wrong? Thanks!
In my project, I need share the SBO data to 3rd party company via EWS. I have installed SmartConnector, added and configured SOAP EWS Rest Provider, and also tested successfully in Swagger. I attempted to do further testing using the SOAPUI tool, but didn't succeed.
BRs / Jessie
Link copied. Please paste this link to share this article on your social media post.
Create your free account or log in to subscribe to the forum - and gain access to more than 10,000+ support articles along with insights from experts and peers.