Jens L.

Commented on Issues Connecting Claude Desktop to SnapLogic via...·Posted inCommunity Questions

(edited)·

Hi Prakhar, I also had issues connecting Snaplogic MCP server to claude desktop via the customize->connectors So I did another approach:

Open Claude Code in claude desktop give it the server url from the MCP you created in snaplogic
Also give it the info of the authentication policy

I created an API Key authenticator policy
tested out with a key and told claude code

Server URL
API-Key-Header
The value of the key

Result: Claude adds the MCP server and the connection works Let me know if this works fro you

Commented on Best Architecture Practices for API Management and...·Posted inSnapLogic Best Practices

Jens L.

Thank you for the detailed feedback Kams N. and Adam N.. Now it is much clearer to me! This will help me a lot for future projects. Like mentioned it always depends one the use-case and if it is an edge-case.

Posted in SnapLogic Best Practices·

Jens L.

Best Architecture Practices for API Management and Consumer Access Control

Hello everyone, I have a question concerning the API manager. So in the past we have mostly worked with API policy manager and creating Api Keys (associated with a role) for the consumers. My question: Which architecture or best practice do you use when it comes to creating and publishing APIs:

1.
Create one API with api Keys (and roles so you can use expressions in the policies that they can only use certain endpoints) and send it secure to the consumer.

a.
e.g I have an api key that is associated with role generalRead -> in the authorize by role policy I write the condition: request.method == "GET"

3.
Create multiple small APIs and publish them with a subscription (subscriptions manager). So that you can manage which parts consumers can use of the APIs combined.

myapi-public (only allowed endpoints)
myapi-admin (restricted endpoints)

d.
myapi-write (write endpoints)

4Comments

About

Company
Title