Jonathan Turner 3196640dcd Version 8 hace 6 años
..
docker 3196640dcd Version 8 hace 6 años
krb5kdc-vagrant 3196640dcd Version 8 hace 6 años
krbclient-vagrant 3196640dcd Version 8 hace 6 años
krbhttp-vagrant 3196640dcd Version 8 hace 6 años
latest-krb5kdc-vagrant 3196640dcd Version 8 hace 6 años
mit-krb5kdc 3196640dcd Version 8 hace 6 años
older-krb5kdc-vagrant 3196640dcd Version 8 hace 6 años
ActiveDirectory.md 3196640dcd Version 8 hace 6 años
README.md 3196640dcd Version 8 hace 6 años
http.testtab 3196640dcd Version 8 hace 6 años
sysHTTP.testtab 3196640dcd Version 8 hace 6 años
sysHTTP_RES.GOKRB5.testtab 3196640dcd Version 8 hace 6 años
testuser1-USER.GOKRB5.testtab 3196640dcd Version 8 hace 6 años
testuser1.testtab 3196640dcd Version 8 hace 6 años
testuser2-USER.GOKRB5.testtab 3196640dcd Version 8 hace 6 años
testuser2.testtab 3196640dcd Version 8 hace 6 años
testuser3.testtab 3196640dcd Version 8 hace 6 años

README.md

gokrb5 Integration Test Environment

Below are some instructions for how to run the network services required for the gokrb5 integration tests.

There are two options to run these services.

  1. As docker containers directly on your machine.
  2. As a vagrant VM instances.

Docker Containers

The Docker containers can be run with the commands you see in the before_install section of the .travis.yml file. You will need to set the environment variable TEST_KDC_ADDR to "127.0.0.1" when running the integration tests.

Vagant VM Instance

The Vagrant VM instance has been configured to work with VirtualBox. VirtualBox will need to be configured with a host network. In the Vagrantfile configuration the CIDR range for that network is assumed to be 10.80.0.0/16 and the instance will run on 10.80.88.88. If this does not work for your environment you will need to update the Vagrantfile accordingly and when running the integration tests set the environment variable TEST_KDC_ADDR to the IP you have allocated for this Vagrant instance.

Running the Integration Tests

Ensure you have set the environment variable TEST_KDC_ADDR accordingly.

To run the integration tests pass -tags=adintegration as an argument to the go test command. This will run all unit and integration tests (other than the integration tests for Active Directory).