search results

(...) cycle requirements At the initial configuration phase, the Integrator delivers the “Hello World” interface in order to check communication process and  inspect whether possible authentication is required. Along with the web service or procedure the Integrator delivers an exemplary message invocation together with expected feedback message (either “an error” or “a succe (...)

(...) n with configuring REST connection from REST API Autenti.   Figure 5. API connection configuration   Create “REST Web Service” connection and select Salesforce authentication . Using data from Autenti account, enter “Client ID” and “Client Secret”. URL addresses are valid as of 4th July 2022. When configuring the connection check the up-to-date vers (...)

(...) TTP protocol. Applying automatically generated certificates makes it possible to work on several stations in domainless environments and prevents wrong configurations of the said environments and the authentication system.

(...) s configured on BPS Portal and only after launching the provided address, it will transfer you to the log-in panel. Further changes include deletion of “save password” and “external authentication ” parameters – from now on both settings are “true” by default. BPSX file structure As previously BPSX is an XML format file and allows to define all necessary profile pa (...)

(...) d in OData format and used in Power BI Desktop and Online. This greatly simplifies WEBCON integration with Power BI, instead of manually constructing REST API queries and dealing with token-based authentication , we are able to use one of two custom connectors to easily load data from WEBCON BPS into Power BI. Handling this data is also less cumbersome, we are able to apply filtering to the data and sele (...)

(...) the use of another license. If the container has been properly disabled, the license is released. A report on the licenses used is available in WEBCON BPS Designer Studio. In addition, an external authentication provider, e.g. Azure Active Directory or OpenID Connect, will be required as Windows authentication does not work properly in containers.   Log in to WEBCON BPS Portal by entering the adm (...)

(...) eration. This article details the Path transition authorization and related system changes.   Configuration and operation principles Path transition authorization provides additional authentication that prevents unapproved access to tasks in the process. This protects against unauthorized use, such as when an employee leaves their workstation and another employee occupies it. Access to the data (...)

(...) rds available in WEBCON BPS Designer Studio's License management window. Follow these steps to prepare your environment for license activation: Log in to Designer Studio by selecting the authentication method and entering the login and password configured during program installation. Open the program’s main menu by clicking the icon in the upper left corner of the screen and select Li (...)

(...) edded in WebView, most functionalities available in the mobile application are supported in a manner similar to how they are supported in regular desktop browsers. It is important to mention that authentication is a special case in this scenario. This is the only functionality associated with the mobile application which requires access to an internet browser. Below are the functionalities listed based o (...)

(...) rios where it has already been enabled.   Extended Protection and connectivity issues The Extended Protection feature adds an additional layer of protection by requiring stronger client authentication and securing client-server communication. However, activating this feature can lead to a number of connection issues in specific scenarios, such as environments utilizing SSL offloading, or situation (...)

(...) t ARR with Cookie Affinity enabled. Only the subscription licensing model is supported. Perpetual licenses cannot currently be used. Containerization is supported from version 2023 onward. User authentication based on AD is not currently supported. Use Entra ID, ADFS, or any other provider that supports OpenID Connect. If the SOLR component is to be implemented in a cluster, it will require persistent s (...)

(...) configuration should protect all endpoints where a user is authenticated based on cookies provided by the browser. As for headers which are omitted – this is for when endpoints rely on token authentication . This list of exceptions here should contain all such endpoints.   Logout options in Portal By default, we have one logout button which logs out of one session. We can add a second but (...)

(...) ueries and test functionalities.   Order of calling methods The following is the order of calling new methods in Swagger for testing the automatic import functionality: Perform an authentication operation. Select the API definition in the upper right corner of the screen. In the Account section, select Try it out and fill in the grant_type, client-id, and client_secret fields with data from (...)

(...) uced the functionality to invalidate all active user sessions with the Global logout button. When the button is pressed, the user is logged out of all environments and platforms that use cookie-based authentication , including web browser tabs and windows, the mobile app, WEBCON BPS Teams, Outlook Classic, and Outlook Modern add-ins. This article outlines the key considerations related to this functionality a (...)

(...) the use of another license. If the container has been properly disabled, the license is released. A report on the licenses used is available in WEBCON BPS Designer Studio. In addition, an external authentication provider, e.g. Azure Active Directory or OpenID Connect, will be required as Windows authentication does not work properly in containers.   Log in to WEBCON BPS Portal by entering the adm (...)

(...) Warning, which logs events starting from unexpected issues. However, to specify a log level for a particular provider, add a new row and insert the specific component, i.e., Microsoft.AspNetCore.authentication (indicates that a user logged into Portal) or Microsoft.AspNetCore.Authorization (indicates the authentication method selected by the user). Next, enter the log level after the colon by typing Inform (...)

(...) tailed description of the functionalities mentioned herein and their configuration can be found in the following sections of the WEBCON BPS Help: Users and groups synchronization | WEBCON BPS authentication providers | WEBCON BPS   Introduction Microsoft Entra ID (formerly Azure Active Directory) enables secure identity management and control of access to cloud resources and on-premises (...)

(...) in many ways a continuation of that feature. The terminology and approach are carried over.   Configuration and operation principles The access authorization feature provides additional authentication , protecting sensitive data on the form. When users open a form, they cannot interact with the protected data until they confirm their identity. This can reduce the risk of unauthorized people gai (...)

(...) wing sections of the WEBCON BPS Help: Security | WEBCON BPS SMS notifications | WEBCON BPS   Introduction SMS notifications in WEBCON BPS are one of the methods for additional authentication of user operations, e.g. when authorizing path transition or access to confidential form data. This article provides instructions on how to configure an SMS gateway that allows sending short text mes (...)

(...) otes.de I wasted quite a lot of time when setting up an App registration to upload documents to SharePoint using REST actions in WEBCON.  Since WEBCON BPS 2025 does not support certificate authentication I had to persuade SharePoint to allow Client id/secret authentication .  Maybe I did something wrong, but I also was not able to use the build in OAuth authentication option. Therefore, I added (...)