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

Get the global settings of the client that runs the transform #50

Open
nosid91 opened this issue Feb 27, 2023 · 5 comments
Open

Get the global settings of the client that runs the transform #50

nosid91 opened this issue Feb 27, 2023 · 5 comments

Comments

@nosid91
Copy link

nosid91 commented Feb 27, 2023

Is it possible to get global client settings in Transform? For example, do I want to know the user's license number or id and make sure that this person is the one doing the transforms?

@cmlh
Copy link
Contributor

cmlh commented Jun 5, 2023

An API Key et al are configured by a Maltego Transform Setting.

@nosid91
Copy link
Author

nosid91 commented Oct 18, 2023

@cmlh The API key has nothing to do with it. I am interested in getting information about the client's license from the code. I need to identify that a particular user is using the transform with his API key and has not shared it with a third party

@crest42
Copy link
Collaborator

crest42 commented Oct 23, 2023

We purposfully prevent sending any license key or other user identifier to preserve the privacy of our users. Can you describe your setup in a bit more detail? Are you using the pTDS or an iTDS setup?

@nosid91
Copy link
Author

nosid91 commented Nov 8, 2023

@crest42
We are using pTDS for now. It is just important for us that the API key to be used by users should not be used by other users than those who own it.
But thanks for the info!

@crest42
Copy link
Collaborator

crest42 commented Nov 9, 2023

Right now we are not sending any license information when runnning transforms against the pTDS for the above reasons. However, we are currently evaluating a similar requirement from another user and may introduce a change. Since this is not a TRX issue, I would advise you to contact support@maltego.com for more visibillity regarding that change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants