Jonathan Turner cbdf1c7592 fix failing pre-auth on TGT renewal when client's prefered etype is not há 7 anos atrás
..
docker cbdf1c7592 fix failing pre-auth on TGT renewal when client's prefered etype is not há 7 anos atrás
krb5kdc-vagrant b77c1e4a4c fix integration test kdc config há 7 anos atrás
krbclient-vagrant c7bc1c0d0d golint fixes and new krbclient vagrant há 8 anos atrás
krbhttp-vagrant cfa6e89a3b test against mod_auth_gssapi há 7 anos atrás
latest-krb5kdc-vagrant b77c1e4a4c fix integration test kdc config há 7 anos atrás
mit-krb5kdc 72011f9c07 red dom testenv há 8 anos atrás
older-krb5kdc-vagrant b77c1e4a4c fix integration test kdc config há 7 anos atrás
ActiveDirectory.md f5dd6dff87 fix identity realm há 7 anos atrás
README.md 79866d016e contribution guidelines há 8 anos atrás
http.testtab 3b1435f16b testenv há 8 anos atrás
sysHTTP.testtab 72bc7f381d pac tests há 9 anos atrás
sysHTTP_RES.GOKRB5.testtab e4f1ffe3cb test data and target correct kdc há 8 anos atrás
testuser1-USER.GOKRB5.testtab e4f1ffe3cb test data and target correct kdc há 8 anos atrás
testuser1.testtab d3bdd4d8c6 support for rc4-hmac enctype há 8 anos atrás
testuser2-USER.GOKRB5.testtab 1010d14c54 fixes to PAC decoding há 7 anos atrás
testuser2.testtab d3bdd4d8c6 support for rc4-hmac enctype há 8 anos atrás
testuser3.testtab d3bdd4d8c6 support for rc4-hmac enctype há 8 anos atrás

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).