Skip to content

Steffen Guertler

My feedback

2 results found

  1. 13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Atlas » Alerts  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Steffen Guertler supported this idea  · 
  2. 31 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Atlas » IAM  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Steffen Guertler commented  · 

    We https://bosch-iot-insights.com are migrating from an on-prem MongoDB to Atlas and also miss this feature heavy.
    As the original poster, Matt, says, in Azure, all the micro services already got their own AD representation, called "(managed) service principals".
    Being able to use those also for MongoDB access avoids to manage another representation of those services, through current technical database users in Atlas: Effectively, no automation code would be needed to reflect the dynamic come and go of new micro services.
    Like with the LDAP adapter, just having a "AD group" to db-permission mapping would be enough to allow micro services access to a database.
    In our particular case, we're representing all our customers as a bunch of agents, each an own micro service in Azure, i.e. we've hit the "no-more-than-100" database users already and would even need more than the hard limit of 1000 users.

    Steffen Guertler supported this idea  · 

Feedback and Knowledge Base