You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
** Adjust URL of the Kerberos buildpack to latest version. You can get the full zip URL from [Releases](https://github.com/macsux/kerberos-buildpack/releases) page.
34
+
33
35
## How it works
34
36
35
37

@@ -49,26 +51,22 @@ Recommendation is to start with sample app included, which exposes the folowing
49
51
50
52
After the app starts up you should see logs emitted from sidecar process that look like this:
2022-01-26T19:04:14.75-0500 [APP/PROC/WEB/0] OUTEnsurethatthefollowingSPNfor the service exists: http/kerberosdemo.apps.longbeach.cf-app.com
65
60
```
66
61
62
+
* sidecar logs may be intermixed with app logs
63
+
67
64
If you have not received a message similar to `Service authenticated successfully as 'iwaclient'`, it means that the worker sidecar has been unable to obtain ticket from your KDC.
68
65
69
66
#### Things to check
70
67
71
68
- Sidecar process started, as indicated by log entry containing `Now listening on: http://0.0.0.0:9090`. (noteport9090-theremaybesimilarlogentrybutforport8080-thatoneisforthemainapp).
Console.WriteLine($"Sidecar process startup script installed into $HOME/app/profile.d/{startupScriptName}");
48
52
// below code attempts to use official way to introduce sidecar via buildpack as described here https://docs.cloudfoundry.org/buildpacks/sidecar-buildpacks.html
49
53
// except it doesn't work and staging never completes - just hands with no error. workaround for now is to have process started as a background executable
50
54
// stuffed into .profile.d startup script, but this makes logs emitted by sidecar show up as if originating from app
0 commit comments