andrew11

We also need this. We are required to use 2FA/MFA that is compliant with AAL level 3:

Setting_up_your_Okta_org_for_Fedramp_compliance_0.pdf

Alternatively, the setting could be ignored for administrators.

I think the software already ignores a few settings if the user is an 'administrator'. For example, even though I set the "View' permissions to "Never" for some folders, those folders are still viewable by administrators.

Thanks!

Our folders within the enterprise data source are structured as shown below. Within each of the 'tiers' we have all of our sessions (a mixture of RDP, SSH, Web Browser, etc.).

In our enterprise, we use concept of "least privilege" and we assign user group permissions directly to each session entry (each server). We have a separate user group for each application that our staff is supporting and we add users to those user groups when they have a need to support those applications. This also helps keep the number of items a staff member can see to a bare minimum, so they don't get overwhelmed. But this sometimes results in many empty folders/subfolders. It would be useful to have an option to hide empty folders. I assume this would be a client-side option and I'd request that we could control it using group policy (or set it at the data source level).

• Infrastructure

  • Location 1

    • Production

      • Web Tier

      • App Tier

      • Database Tier

      • Utility Tier

    • Development

      • Web Tier

      • App Tier

      • Database Tier

      • Utility Tier

    • Testing

      • Web Tier

      • App Tier

      • Database Tier

      • Utility Tier

    • Staging

      • Web Tier

      • App Tier

      • Database Tier

      • Utility Tier

  • Location 2

    • Production

      • Web Tier

      • App Tier

      • Database Tier

      • Utility Tier

    • Development

      • Web Tier

      • App Tier

      • Database Tier

      • Utility Tier

    • Testing

      • Web Tier

      • App Tier

      • Database Tier

      • Utility Tier

    • Staging

      • Web Tier

      • App Tier

      • Database Tier

      • Utility Tier

  • Location 3

    • Production

      • Web Tier

      • App Tier

      • Database Tier

      • Utility Tier

    • Development

      • Web Tier

      • App Tier

      • Database Tier

      • Utility Tier

    • Testing

      • Web Tier

      • App Tier

      • Database Tier

      • Utility Tier

    • Staging

      • Web Tier

      • App Tier

      • Database Tier

      • Utility Tier

  • ... ... ... ...

+1 of SAML/OAuth2/OpenID, so we can use Okta.

I'm happy to offer up my Okta tenant for testing.

I have bug report for Devolutions Server, regarding Email configuration.

Our mail relay server does not require username/password authentication. But there is no option for "anonymous" when setting up the email settings.

But I figured out, if you just put a "space" character for username and for password, then the "Test Email" button works.

We also are required to use Integrated Authentication. This bug prevents our staff from responding to emergency infrastructure outages from a remote location. Hoping this get resolved soon. Thank you.