Impact 2024: The Industrial Data and AI Conference for and by Users | Nominate Speakers Now for a Ch...
I found the problem. It was the incorrect {{project}} in the url. Changed it to the correct one and it works correctly
This is a better view of the yml content from the above posting ---bootstrap: features: with-special-groups: false with-raw-capability: true aggregated-level-name: all group-prefix: test dataset-suffix: ds rawdb-suffix: db rawdb-additional-variants: - state idp-cdf-mappings: - cdf-project: myproject mappings: - cdf-group: test:all:FTDM_Users idp-source-id: 5b20d90a-648f-4005-89df-da9bc3d122b3 idp-source-name: SWC_DATA_FTDM_Users namespaces: - ns-name: src description: Data sources for the extractor ns-nodes: - node-name: src:001:fteg description: Source 01 Data cognite: host: ${BOOTSTRAP_CDF_HOST} project: ${BOOTSTRAP_CDF_PROJECT} idp-authentication: client-id: ${BOOTSTRAP_IDP_CLIENT_ID} secret: ${BOOTSTRAP_IDP_CLIENT_SECRET} scopes: - ${BOOTSTRAP_IDP_SCOPES} t
Thanks. I changed the groupnames to all:owner and all:read and it works like a charmI still find it “disappointing” that you’re limited to those names but they’re usable so that’ll work
Hi Peter Thanks for that further explanation. Based on the constraints, I appreciate why you limit the groups to “owner” and “read”Before I respond to your request for what I meant by “disappointing”, let me describe my setup that I was trying to map over to CDF.My AAD Groups might have names like SuperAdmins, Constributors, Developers. I was then trying to map those to CDF groups with the same names (which would then be given appropriate capabilities to line up with their intended scope). This is when I hit the snag. I can’t map to groups ending in anything other than “owner” or “read”.What I suppose I am saying I would like to be able to do (notwithstanding the constraints you describe) is to be able to define groupnames in a custom fashion and not be limited to “owner” and “read”.I understand that you can use Namespace and Nodes to create custom nodes in the namespace but (please correct me if I am mistaken in the following statement) these would not automatically tie up to the asso
Thanks EinarThat is very helpful
Our testing can’t reproduce the problem so I think it is fixed
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
