search results

(...) Introduction   WEBCON BPS 2021 R5 and 2022 R3 versions allow users to configure Portal–Service connection. Until now, such communication took place only via the SSPI-protected HTTP protocol . Now users can change the type of communication to NetTCP protocol secured by automatically generated certificates.    Configuration   The default communication method set (...)

(...)       If you have an optional key certificate, you can select it in the next step but here it is not needed and you can go further. The next step is to select the protocol in which ADFS will communicate with WEBCON BPS application – BPS is the application supporting the Windows Federation protocol so you must select this option and enter the Portal address as the (...)

(...) er installing WEBCON BPS, the privileges can be downgraded to db_owner. For integration purposes: Portal URL address. Azure Active Directory requires that the address adheres to HTTPS protocol . Trusted SSL certificate installed on the machine. “Self-signed certificate” will not work. Registered applications in the AAD management panel. Their configuration is covered below. (...)

(...)   Fig. 7. The OAuth client configuration   Creating tokens To create a refresh token, make two invokes – see here: https://developers.google.com/identity/protocol s/oauth2/native-app#loopback-ip-address. The first invoke is used to obtain the authorization code. In the following call you must replace {ClientID} with the correct Client ID described in th (...)

(...) ssigning an SSL certificate. The binding for port 80 is enough because the communication between WEBCON BPS Portal hosting Web Server and Reverse Proxy Server takes place through the unencrypted http protocol . The last important thing is to configure the WEBCON BPS Portal address - this address should be configured to use the https protocol . The address can be changed by using the “Tools for (...)

(...) you can extend the configuration of pages with additional elements such as tables or information for application users. If you want to add the embedded elements to this module, you must use the https protocol address.   Fig. 12. The configuration of the HTML code element   Find instance The Find instance widget allows you to search for phrases in the application. The availabl (...)

(...) ovider’s side, in this case, Google. The configuration is described here. Integration of the authentication provider in WEBCON BPS requires the provider to fully implement the OpenID Connect protocol . It is necessary that the endpoint with metadata (autodiscovery) is available at <Authority>/.well-known/openid-configuration. During registration, we will obtain the data necessary for conf (...)

(...) gt; https://www.keycloak.org/docs/latest/getting_started/index.html#creating-a-realm-and-a-user. Next, register the application client. Go to the Clients tab -> Create, and in the “Client protocol ” field enter openid-connect.     After saving, complete the remaining configuration fields: In the Access Type field, select confidential. In the Root URL field, (...)

(...) guration for SharePoint Server 2016). Requirements   Azure Active Directory catalog with Azure AD Premium P2 license.     Web application working on HTTPS protocol     Configuration of new Azure AD application This chapter is dedicated to a step-by-step configuration of Enterprise application Azure AD which is our external authentica (...)

(...) tion will not allow attachments to be edited directly from the form viewed in WEBCON BPS Portal and using the desktop version of Microsoft Office. To edit files on the form, WEBCON BPS uses WebDav protocol s. Microsoft does not support using WebDav protocol s in desktop products while using Google Identity as the external authentication provider. Trying to edit a file in such a scenario will result i (...)

(...) ing cliconfg.exe, open the ”Alias” tab. Press the ”Add” button and add a new alias.     In the displayed window enter the right configuration for: protocol , alias name, new server name, new server port – uncheck the checkbox and fill-out if other than the default one.     A configured alias appears once you click &ld (...)

(...) er you created earlier: nbdemo.webcon.pl:48440 {    tls /etc/caddy/cert.pem /etc/caddy/key.pem    reverse_proxy bps_portal:48441 } Reverse proxy uses the https protocol . For the reverse proxy address to be trusted, use a trusted certificate for the test computer address. To do this, place the cert.pem and key.pem files with the certificate in the current folder. & (...)

(...) mponents. Two pillars of the aforementioned standard are made available, i.e. traces and metrics (currently WEBCON BPS does not support logs within the context of OpenTelemetry). Besides the OTLP protocol (OpenTelemetry protocol ), which forms a part of the OpenTelemetry project, it is possible to use the Jaeger platform for collecting and processing traces, and the Prometheus tool to receive and analy (...)

(...) ey are not necessarily implemented by every authentication provider: - 'Official': https://openid.net/specs/openid-connect-core-1_0.html#AuthRequest - Google: https://developers.google.com/identity/protocol s/oauth2/web-server#creatingclient - Microsoft: https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-auth-code-flow 2. Those who are using custom endpoints will know what they are (...)

(...) ith adding entries to Exchange callendars through action and e-mail sending? Recently Microsoft stopped support of basic auth... Oh, I forgot to mention: I have reactivated Basic Auth for all the protocol s available in the article https://techcommunity.microsoft.com/t5/exchange-team-blog/basic-authentication-deprecation-in-exchange-online-september/ba-p/3609437 . Still no luck... maybe some more time (...)