My TIB is not a docker container. I just follow the setup tutorial and start ./tib in my EC2 linux prompt.
My custom provider is running inside a container but as you say earlier, you succeed in calling it.
Here the content of my tib.conf (just in case) :
"Secret": "test-secret",
"HttpServerOptions": {
"UseSSL": false,
"CertFile": "./certs/server.pem",
"KeyFile": "./certs/server.key"
},
"BackEnd": {
"Name": "in_memory",
"ProfileBackendSettings": {},
"IdentityBackendSettings": {
"Hosts" : {
"localhost": "6379"
},
"Password": "",
"Database": 0,
"EnableCluster": false,
"MaxIdle": 1000,
"MaxActive": 2000
}
},
"TykAPISettings": {
"GatewayConfig": {
"Endpoint": "http://localhost",
"Port": "8080",
"AdminSecret": "54321"
},
"DashboardConfig": {
"Endpoint": "http://localhost",
"Port": "3000",
"AdminSecret": "12345"
}
}
}
And I also tried to curl my custom provider from the TIB EC2 VM
curl -X POST http://54.194.61.205:8888/auth
And it works fine relying : {“user_name”:“toto”} (http 200)