Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using SQL API the extendContext function does not get the securityContext created in checkSqlAuth #7415

Open
giacomochiarella opened this issue Nov 14, 2023 · 2 comments
Labels
api:sql Issues related to SQL API backend:server Issues relating to Cube Core's Server enhancement New feature proposal

Comments

@giacomochiarella
Copy link

Describe the bug
Hi everyone! I’m using the same cube.js file but I’m getting different results when I access to the securityContext in extendContext function:

  • if I use the rest api I get a big object with securityContext attribute
  • if I login through dbeaver I get only { id: ‘d8ce5857-500d-4c10-a9fb-40408cc9986c-span-1’, meta: null }

in checkSqlAuth I’m returning a securityContext like:
return {
password: password,
securityContext: securityContext
};

To Reproduce
just login through SQL API and print the context in extendContext function

Version:
0.34.7

@igorlukanin
Copy link
Member

Thanks for posting this, @giacomochiarella 👋 I think this is a known limitation.

@igorlukanin igorlukanin added enhancement New feature proposal backend:server Issues relating to Cube Core's Server api:sql Issues related to SQL API labels Nov 30, 2023
@HaidarZ
Copy link
Contributor

HaidarZ commented Jan 23, 2024

+1
I cannot neither read the securityContext from the contextToAppId nor from inside the asyncModule via the COMPILE_CONTEXT

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api:sql Issues related to SQL API backend:server Issues relating to Cube Core's Server enhancement New feature proposal
Projects
None yet
Development

No branches or pull requests

3 participants