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.

Sign up for GitHub

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

Jump to bottom

QZDASOINIT Special registers with client information #83

Open
GautierFR opened this issue Nov 4, 2024 · 3 comments · May be fixed by #93
Open

QZDASOINIT Special registers with client information #83

GautierFR opened this issue Nov 4, 2024 · 3 comments · May be fixed by #93
Labels
enhancement New feature or request

Comments

@GautierFR
Copy link

As part of the implementation of exit programs on the QZDASOINIT / QZDASSINIT jobs to control traffic, it appears in the joblog that the connection is made from client 127.0.0.1 (which is normal, since the connection comes from of mapepire-server which runs on the same server).
I noticed that there was the client IP address information in the special CLIENT_WRKSTNNAME register but only in certain cases and not all the time. We cannot consider this information as "reliable".
Would it be possible to send information from the mapepire client permanently to be able to apply more precise filtering rules in exit programs?
What do you think ?
@worksofliam
Copy link
Collaborator

It's a good idea. I believe it's up to each client to set this independently of the server.

For example, here's the Node.js config: https://github.com/Mapepire-IBMi/mapepire-js/blob/main/src/sqlJob.ts#L188

@worksofliam worksofliam added the enhancement New feature or request label Nov 4, 2024
@GautierFR
Copy link
Author

Thank you for your answer and consideration.
I see the client config part. But I think it's tricky to apply server-side security rules when the information depends on a client configuration.

@ThePrez
Copy link
Collaborator

ThePrez commented Nov 8, 2024

I agree. This should be implemented in the server component

@ThePrez ThePrez linked a pull request Jan 2, 2025 that will close this issue
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
3 participants
@worksofliam @ThePrez @GautierFR