SSO integration with custom private network #986
-
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Great question, will check and get back to you |
Beta Was this translation helpful? Give feedback.
-
We don't currently support custom chain configs within the auth-server! SSO is still in a beta testing phase (0.0.0-beta13 as of this writing), so we don't have an auth-server with a main-net target. Even if we did, there are a number of custom chain configuration steps we're still documenting that cause this to be quite complicated: https://github.com/matter-labs/zksync-sso/tree/main/packages/auth-server#how-to-deploy-to-a-new-chain Once we've fully released the SDK to main-net, we'll also have better instructions for chain operators to add their AA factories to the SDK for support. If you are currently working on supporting a custom chain with an auth-server, I'd love to know more about your use case so that the first 1.0 release can meet your needs! In practice, if you are planning on forking or contributing a chain, we're attempting to split these kinds of configs into their own files (note the era-sepolia.json in the same folder), so chain operators can provide their deployment addresses. |
Beta Was this translation helpful? Give feedback.
We don't currently support custom chain configs within the auth-server!
SSO is still in a beta testing phase (0.0.0-beta13 as of this writing), so we don't have an auth-server with a main-net target. Even if we did, there are a number of custom chain configuration steps we're still documenting that cause this to be quite complicated: https://github.com/matter-labs/zksync-sso/tree/main/packages/auth-server#how-to-deploy-to-a-new-chain
Once we've fully released the SDK to main-net, we'll also have better instructions for chain operators to add their AA factories to the SDK for support. If you are currently working on supporting a custom chain with an auth-server, I'd love to know more about…