Update stale articles

[jmunsch]

Why close these? When stuff goes stale, it seems like it’d be helpful for the community to pitch in and reply with updated info?

Are you serious I can’t include links in a post?

Stale ( also highest in search engine results ):

• /t/openapi-specification-for-the-auth0-management-api/168929
• /t/openapi-spec-swagger-representation-of-the-auth0-management-ap/169994

Not Stale:

• /t/openapi-3-0-specification/111861

Please , Update your stale knowledge articles:

• auth0 com/docs/api/management/v2

[teodor.andrei]

Hi @jmunsch, and welcome to the Auth0 Community!

Not being able to include links in posts as a new Community user is a security measure to keep the Community free of spam and phishing links.

Thank you for the suggestion regarding the knowledge articles! I will take it to my colleagues so we can update them properly.

Have a great day!
Teodor.

[teodor.andrei]

Hi again, @jmunsch!

I talked to the team about your feedback. The newest version of the OpenAPI specifications, v3.1 schema, is currently in early access. You can find this information in the docs. As for the Knowledge Article, a colleague will update it as soon as possible.

Thank you again!
Teodor.

[jmunsch]

@teodor.andrei Thanks, I’ll be loading this into Prism, so I can stub out an implementation against a mock server.

Much appreciated.

For some reason I wasn’t able to find a docker image of the core community edition, which I suppose is a separate issue.

Evaluating Keycloak as well.

Thanks

[jmunsch]

# Use Node.js base image
FROM node:18-alpine

# Install Prism CLI globally
RUN npm install -g @stoplight/prism-cli

# Create working directory
WORKDIR /app

# Copy the API spec into the image
COPY json/auth0.openapi-311.spec.json /app/auth0.openapi-311.spec.json

# Expose Prism server port
EXPOSE 8083

# Run Prism mock server on port 8080 using the copied API spec
CMD ["prism", "mock", "/app/auth0.openapi-311.spec.json", "--port", "8083", "--host", "0.0.0.0"]