search results

(...) th transition .and prevents the execution of an unrequested task, such as signing a contract. If enabled, users who want to proceed to the next step must confirm their identity based on an additional authorization operation. This article details the Path transition authorization and related system changes.   Configuration and operation principles Path transition authorization provides addition (...)

(...) POST method https://graph.microsoft.com/v1.0/groups/{group_id}/calendar/events The api needs to run in the context of the logged in user, not in the context of the application. That's why I added authorization s in webcon: screen1 I added a connection to this authorization : screen2 Then in the REST action I added this connection. On the graph api side, added Group.ReadWrite.All delegated permissions, (...)

(...) Hi, I really like the new path authorization feature and we will surely use it. The geolocation is also an interesting addition but if it's used in combination with the path authorization it will created unexpected results. I noticed that the geolocation of the browser is used, even if path authorization with method "application" is used. If this method is used, it would be great to use the location of t (...)

(...) Hi, as always when a new feature is provided, new requests will follow immediately. :) It would be great to see in the workflow history whether path authorization was used and which method was used. At the moment, it's not at all visible if path authorization was used at all. If the authorization is activated for existing workflows, we can't distinguish which instances have been using it. Best r (...)

(...) orting/exporting.   SharePoint library Storing files in the SharePoint library allows you to easily share and catalog them. All documents can be easily accessed from mobile devices. The authorization management system allows access to add or edit content only to persons authorized to do so. The files can be edited simultaneously by several people and their subsequent versions are possible to be i (...)

(...) create a refresh token, make two invokes – see here: https://developers.google.com/identity/protocols/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 the previous chapter. https://accounts.google.com/o/oauth2/v2/auth?scope=https://www.googleapis.com/ (...)

(...) le':['Role','dataReaderRole']}}" $BodyUserRole = "{'set-user-role': {'WEBCONBPS': ['Role']}}" $Url = "http://solr:8983/solr/admin/authorization " Invoke-RestMethod -Method 'Post' -Uri $url -Credential $Cred -Body $BodyPermission -headers $headers Invoke-RestMethod -Method 'Post' -Uri $url -Credential $Cred -Body $Bo (...)

(...) s administration panel, two concepts should be introduced: Authentication – the process of verifying a user’s identity through a login and password, one-time password tokens, etc. authorization – the process following user authentication, that checks if a user has access to a given resource, etc.   Adding a user via administration panel is used to authorize and enable acc (...)

(...) ReturnedValueType = 5   and users. BRD_IsLocal = 1   Summary The presented reports and queries can be used immediately, or they can be the basis for creating your own reports on authorization s; for example: •    In multilingual environments, you can add translations for application names, workflows, and form types. •    You can associate a workflo (...)

(...) ngs to manage.   Identity verification with security codes   Starting from the 2023 R2 version, it is possible to enhance the security of public links by utilizing a single-use authorization code which is sent to the email address of the link recipient. This solution prevents individuals who have accidentally obtained the link from gaining unauthorized access to the shared instance. & (...)

(...) quals sign and remove the space to the right of it in the headers line. Therefore, the data used in the discussed case are the following: - endpoint: https://otelcol.aspecto.io:4317, - headers: authorization =b29ac31c-789a-4fd1-a389-d47bf854cdee. Additionally, remember to change the Enabled parameter to “true” in the Otlp and Tracing nodes and the Otlp subnodes belonging to the Exporters no (...)

(...) curity section) in Profile settings. A window is displayed where you need to specify the device name and press the Verify button.   After this operation, a message containing a 6-digit authorization code (token) will be sent to the email address you used to register in WEBCON BPS, or, depending on the configuration, via an SMS message. The authorization code remains active for 4 minutes, bu (...)

(...) ication which requires access to an internet browser. Below are the functionalities listed based on how they are supported:     Native part: Profiles, logins, and PIN authorization Searching for information stored in barcodes and 2D codes PUSH notifications Scanning barcodes and 2D codes Determining exact device location Biometric authorization WebView (...)

(...) e after which it is necessary to reauthorize access to an instance gained by opening the received link. The full writeup of this feature can be found here: Public link.   Additional authorization methods The configuration enables you to designate the methods of additional authorization that the end user can leverage when the additional authorization (path transition authorization , authoriz (...)

(...) out of all sessions, a new OpenTelemetry metric has been introduced. This metric is accessible through the “webcon-workflow-portal-ticket-store-cache” module allowing the display of user authorization identifiers currently stored in the cache memory. Detailed information about OpenTelemetry in WEBCON BPS can be found at https://community.webcon.com/posts/post/opentelemetry-in-webcon-bps/403/3. (...)

(...) fy 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 Information. This will ensure that both the login to Portal and the provider name are l (...)

(...) ttern   https://<<BPS_PORTAL_ADDRESS>>/OAuthFlows/ReceiveTokens   Fig. 3. Sample Redirect URI   In order to properly use the received token, the token authorization option must be enabled in the same window. The "Access tokens (used for implicit flows)" option is used for this. This is where you specify whether operations are performed on a single tena (...)

(...) nbsp;      "Endpoint": "[metricsAddress]",               "Headers": "authorization =[apikey]"             },             "AzureMonitor": { & (...)

(...) " & access_token, data = Json.Document(Web.Contents(api_url, [RelativePath="/api/data/v2.0/db/1/applications/34/reports/79", Headers=[accept="application/json", #"Content- Type"="application/json", authorization =AccessTokenHeader]])), #"Converted to Table" = Record.ToTable(data), in #"Converted to Table"

(...) g__Logged|17_1(ResourceInvoker invoker) at Microsoft.AspNetCore.Routing.EndpointMiddleware.g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger) at Microsoft.AspNetCore.authorization .authorization Middleware.Invoke(HttpContext context) at WebCon.BPSCloud.Portal.Extensions.RouteValuesTypeVerificationMiddleware.InvokeAsync(HttpContext context) at WebCon.BPSCloud.Portal.Exten (...)