10 months ago
moving from owned node fro azure to railway,
we have enterprise license hence we have the ability enable SSO within N8N.
we use google workplace for SSO and it worked well on our Azure Docker n8n deployment.
trying out the same SSO configuration on n8n node after entering in our license number, the SSO is not working.
I tried with Railway domain and custom domain which i own.
was you team able to achieve this?
after proper configuration which worked for Azure docker deployment,
i get the following error message from google workspace SSO test.
Cannot GET /rest/sso/saml/primary-production-9312.up.railway.app/instruction which worked,
8 Replies
10 months ago
Your error logs says the license renewal failed.
Status changed to Awaiting User Response Railway • 10 months ago
unicodeveloper
Your error logs says the license renewal failed.
10 months ago
Thank you I will deactivate the license on the existing node
Status changed to Awaiting Railway Response Railway • 10 months ago
unicodeveloper
Your error logs says the license renewal failed.
10 months ago
which log did you check?
nvm
i can see it in deploy log
10 months ago
i double checked,
not sure if [license] license renewal failed: Too many requests. Slow down! is the root cause of this problem.
10 months ago
looks like SSO is missing the redirect page.
requestId:"ukEou7NJQ0WGcNNXEnTDew_2074704348"
timestamp:"2024-12-23T18:36:00.733387975Z"
method:"GET"
path:"/rest/sso/saml/primary-production-9312.up.railway.app/"
host:"primary-production-9312.up.railway.app"
httpStatus:404
upstreamProto:"HTTP/1.1"
downstreamProto:"HTTP/2.0"
responseDetails:""
totalDuration:12
upstreamAddress:"http://[fd12:7b70:f081:0:8000:1a:6a0a:950]:5678"
clientUa:"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36"
upstreamRqDuration:12
txBytes:192
rxBytes:2355
srcIp:"204.225.214.57"
edgeRegion:"us-east4"
10 months ago
I am really not sure how SSO works in your own service but that has nothing to do with Railway. So maybe look at the service renewal and check how it relates to whatever SSO/Saml you are connecting to
Status changed to Awaiting User Response Railway • 10 months ago
10 months ago
thanks for the reply,
I think it's something to do with license renewal frequency
Status changed to Awaiting Railway Response Railway • 10 months ago
10 months ago
You are welcome
Status changed to Awaiting User Response Railway • 10 months ago
Status changed to Solved brody • 10 months ago