Skip to content
#

access-control

Here are 617 public repositories matching this topic...

graphql-engine
sassela
sassela commented Jun 28, 2021

Issue split from hasura/graphql-engine#6951

our pytest output has a pretty low signal:noise ratio, and it's often difficult to understand the cause of a test failure, if there is one. [Example: a 8600-line log for what turned out to be a flaky test that passed on a second run](https://app.circleci.com/pipelines/github/hasura/graphql-engine-mono/10008/workflows/5e17c7

oso
ximon18
ximon18 commented Mar 18, 2021

With oso 0.11.1 and Rust client code.

When tracking down policy logic failures using the POLAR_LOG=1 environment variable I will see the logging of the execution of all of my inline queries. The problem is that I have lots of these, but usually I'm not interested in the ones in my core policy files which are fairly static and unchanging, but rather I'm interested in those policy sources that

lumjjb
lumjjb commented Dec 10, 2021

Description: Feedback from the Cloud Native Microsurvey has shown that there is a gap in the area of auditing cloud native systems and the use of cloud native technology and security. There are several efforts ongoing that are looking at controls in the group such as the security controls working group, however there is still a gap of widespread knowledge about methodology and techniques of au

zitadel
livio-a
livio-a commented Nov 30, 2021

After creating a custom login policy, the active identity providers are still listed from default. Same ist for MFA and 2FA, ...

From the screenshots below, you can see that the new policy is loaded after creation and reset. But only the policy itself and not the identity providers and factors:
![image](https://user-images.githubusercontent.com/9405495/143998582-86d03161-287f-4448-b0e4-feca882

A tool for logging data/testing devices with a Wiegand Interface. Can be used to create a portable RFID reader or installed directly into an existing installation. Provides access to a web based interface using WiFi in AP or Client mode. Will work with nearly all devices that contain a standard 5V Wiegand interface. Primary target group is 26-37bit HID Cards. Similar to the Tastic RFID Thief, Blekey, and ESPKey.

  • Updated Jan 29, 2022
  • C++

Improve this page

Add a description, image, and links to the access-control topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the access-control topic, visit your repo's landing page and select "manage topics."

Learn more