Closed jpmorrison closed 2 years ago
mstsc.exe can send an empty token and cause the nil pointer
func VerifyPAAToken(ctx context.Context, tokenString string) (bool, error) {
token, err := jwt.ParseSigned(tokenString)
+// log.Printf(" debug verify PAA token %s err %s",token, err)
+ if err != nil {
+ log.Printf(" tokenString = %s", tokenString )
+ log.Printf(" jwt.ParseSigned() failed due to err=%s", err)
+ return false, err
+ }
I can connect with mstsc if I comment out the error return for invalid PAA cookie (server.go) and client host does not match token host (jwt.go)
I don't need the web tokens/oauth right now so a config option for disabling would be nice. NTLM and/or kerberos could work instead.
This is fixed in master. This was an issue with MSTSC being a bit more picky than other clients (rightfully so) on the protocol handshake. It happened when a PAA cookie was required but not send as part of the caps.
first off, can I disable openid? I just want a simple rdpgw I can install standalone on jump box
docs: key(s) in rdpgw.yaml should be only 32 characters - I got an error about crypto/aes key being 33
I downloaded rdpgw-1.0-stable and built rdpgw on ubuntu 20.04
I think I have openid working with Google - looks like Google part works and it redirects me. There's an auth.json with tokens in it. But on https://localhost:9443/connect I get
cannot find session or user
the logs show: