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

API ML: secure credentials store usage implementation #153

Open
KUGDev opened this issue Sep 1, 2023 · 1 comment
Open

API ML: secure credentials store usage implementation #153

KUGDev opened this issue Sep 1, 2023 · 1 comment
Labels
priority-medium Should be resolved in 1-3 sprints
Milestone

Comments

@KUGDev
Copy link
Contributor

KUGDev commented Sep 1, 2023

API ML gives a possibility to auhorize using API ML MFA
We need to investigate this possibility
DoD: the authentication and authorization process is working with API ML (test of z/OSMF connection is successful)

@KUGDev KUGDev added the priority-medium Should be resolved in 1-3 sprints label Sep 1, 2023
@KUGDev KUGDev added this to the 1.2.0 milestone Sep 1, 2023
@dnlsv
Copy link
Contributor

dnlsv commented Nov 10, 2023

First you need to register your z/OSMF service in API ML.

Next you need to specify the z/OSMF Authentication Provider for the API Gateway (https://docs.zowe.org/v2.9.x/extend/extend-apiml/authentication-for-apiml-services/#authentication-providers).

In the file .\api-layer\config\local\gateway-service.yml specify:

apiml.security.auth.provider: zosmf
apiml.security.auth.zosmfServiceId: zosmf # Replace me with the correct z/OSMF service id

To get an API ML token in the cookie you need to send a request:

POST https://localhost:10010/gateway/api/v1/auth/login

Request body:

{
    "username":"username",
    "password":"password"
}

https://localhost:10010 - URL-address of the API ML.
The username and password values are credentials from z/OSMF.

The request will return the value of the API ML token in the cookie (apimlAuthenticationToken), which can be used for next requests without using the Authorization header.

@KUGDev KUGDev modified the milestones: 2.0.0, 2.1.0 Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority-medium Should be resolved in 1-3 sprints
Projects
Status: In Progress
Development

No branches or pull requests

2 participants