Need to query app_metadata in Delegated Admin Extension

[sefa.ilkimen]

Hi guys,

I need to pass a lucene query containing a tenant ID for filtering the user list. So basically, I’m having the same problem mentioned in these topics:

API stopped querying by metadata

Hi, Just about 4…5 hrs ago our requests stopped getting responses from API curl -X GET \ 'https://mobile.eu.auth0.com/api/v2/users?q=app_metadata.person_uuid%3Dae98e42d-1.........' \ -H 'authorization: Bearer eyJ.........' now we receiving ] earlier { "email": ".....@........com", "email_verified": true, "updated_at": "2016-06-03T15:29:47.314Z", "picture": "https://s.gravatar.com/avatar/723d42f66c08........f?s=480&r=pg&d=https%3A%2F%2Fcdn.auth0.com%2…

API User metadata search, am I doing something wrong? -- GET /users

Is this also affected by the new ES clusters? This is what I am using to get all users by “app_id” : https://{{auth0_domain}}/api/v2/users?q=user.app_metadata.app_id:dd This is the POST to create users: { "connection": "email", "email": "jill@jill.com", "user_metadata": {"role":"admin"}, "email_verified": true, "app_metadata": { "app_id" :"dd", "license":"dcfff73c75887787531757c8ca986e47", "tracker":"2" } }

How to search for users by using app_metadata ?

Previously, my API could deliver a list of user to the admin of my app by looking for the value of a property “status” stored in the app_metadata field… Last weeks I found that the API is always returning an empty list, because app_metadata can’t be queried anymore… I have a very few informations to store for each users and that’s why I’m using Auth0 as a database for dealing with users (which are my API’s main objects). My question is : How am I suppose to do now ? Am I forced to store datas…

and many others …

There is also a corresponding incident mentioned there, but the link seems broken: Indexing delays on Search API for Free accounts • Auth0 Status Page

How do I resolve this issue?

[jmangelo]

I’m afraid that if you don’t have a tenant that can perform search over custom metadata fields when using search engine v2 then you won’t be able to accomplish that in the extension. As noted in some of the links you posted this ability it’s not available to every tenant.

There’s a new version of the search engine that is being introduced where the query by a tenant ID in metadata would be possible (Search for Users), however, this is still not generally available and even if you can already use v3 through the Auth0 Management API, the DAE extension is still making use of v2 (auth0-delegated-administration-extension/users.js at b5e3527f30a41df481d6af03cf78a01d98679beb · auth0-extensions/auth0-delegated-administration-extension · GitHub). In conclusion, there does not seem to be a solution for this at this time.

[sefa.ilkimen]

Hmm ok, that’s actually bad news for me Do you have a timeline for when DAE will use search engine v3? I mean in the link you’ve posted it says:

The user search engine v2 will be deprecated soon, so we recommend migrating user search functionality to search engine v3 (search_engine=v3).

So I’d expect DAE to be migrated to v3 very soon?

[jmangelo]

As a personal opinion, soon in software development tends to be a bit more of an unknown then the dictionary definition. What I know is that at this precise time the v3 option is still not generally available so forcing DAE to use it (which would be a quick thing) is not feasible at it would be broken for some. In addition, there are some changes between both engines so even when v2 is deprecated there’s still need to be some time for people to move out of it. With all these in mind I’m a bit unsure in terms of timelines for the DAE. I’ll relay this information internally so that at least I know the possibility to use v3 in the extension is already being tracked.

[jmangelo]

I just wanted to provide you with yet to be confirmed, but possibly some better news related to this. There was work already going for a future release of this extension and the possibility to configure which search engine to use may be included as part of that release so soon in this case may indeed prove to be soon. Have in mind things change, but there’s a good indication that this possibility will land already in the next version (and no, don’t have a timeline for the release of the version).

[sefa.ilkimen]

Ok, that sounds good! Thank you