Uploaded image for project: 'Compass '
  1. Compass
  2. COMPASS-1629

Cross-realm Kerberos Support

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 1.16.0, 1.15.1
    • Affects Version/s: None
    • Component/s: Connectivity
    • None
    • 3
    • Iteration Guacamole, Iteration Halloumi, Iteration Icelandiccharr, Iteration JalapeƱo

      From CS-26551. After a bit of initial investigation, imagine this breaking out into 3 tasks:

      • COMPASS-1629: Spike: Research additional options needed to support cross-realm kerberos via the connect dialog
      • Add additional Kerberos options to connect dialog
      • Kerberos Cross-Realm testing backend setup

      Compass RC1 - Internal Server Error With (Cross Realm) Kerberos @ Connect Time

      Debug Console Shows:

      POST http://localhost:29017/api/v1/token 500 (Internal Server Error)Request.end @ client.js:1016Model.extend.create @ token.js:69(anonymous function) @ token.js:119Item.run @ browser.js:64drainQueue @ browser.js:34_super.bugsnag @ bugsnag.js:149(anonymous function) @ bugsnag.js:624
      bugsnag.js:239 [Bugsnag] Invalid API key 'undefined'
      bugsnag.js:239 [Bugsnag] Invalid API key 'undefined'
      

      Note in the java driver we would have to do something along the following, would this be something that node driver can expose to compass?

              MongoCredential gssAPICred = MongoCredential
                      .createGSSAPICredential(KERBEROS + "@WINDOWSREALM.COM")
                      .withMechanismProperty("REALM", "LINUXREALM.COM")
                      .withMechanismProperty("CANONICALIZE_HOST_NAME", true);
      

            Assignee:
            durran.jordan@mongodb.com Durran Jordan
            Reporter:
            lucas.hrabovsky Lucas Hrabovsky (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: