search results

(...) I greatly appreciate the Access authorization to form fields in WEBCON BPS – it’s a much-needed and well-designed solution that all most meets our needs. Like many other organizations, we handle sensitive data that should not be stored in plain text in the SQL database. To address this, we've developed a simple SDK-based customization of a form field that displays the field value on the form, but stores it (...)

(...) CON application with a banking / core-banking REST API protected by OAuth 2.0 (WSO2). The API is fully standard-conformant (RFC 6749) and supports the following grant types: client_credentials authorization _code password (Resource Owner Password Credentials – intended for trusted internal TSS clients) For the required backend endpoints, the core-banking API supports only user-based tokens obtained via (...)

(...) Hi, REST web services may need some custom headers for authentication, content-type, authorization and so on. Right now one has to configure those custom headers for each REST web services data source and invoke action using the connection. My suggestion is to add default custom headers in the connection as Postman does it in the configuration of its collections. By having this all data sources and i (...)

(...) Referencing also to: https://community.webcon.com/forum/thread/8245 We are integrating WEBCON BPS with APIs that follow RFC 6749 OAuth 2.0 authorization Framework and explicitly support the Resource Owner Password Credentials Grant (grant_type=password). These APIs (in our case: core banking / backend systems) require both: client authentication (client_id / client_secret via Basic Auth) and user aut (...)