{"push_id":1414335914,"size":11,"distinct_size":11,"ref":"refs/heads/5223-send-authn-request-to-connector-node","head":"86bb9ede489efe97d3743f6c17ef0be8b6a29bfe","before":"ccde7f83f3ee9bfcdea11524573a23274686e2c1","commits":[{"sha":"ad2f1298adc995d5d5e17f784f24a14a8636da7e","author":{"name":"Richard Towers","email":"6b5abcb5e5058fa0940d16fafc2b224ff0955dd8@digital.cabinet-office.gov.uk"},"message":"5222: Request metadata from verify\n\nThe bridge should request Metadata from verify on startup, and then\nagain every few minutes (to ensure it stays fresh). It will use this for\nvalidating the Signatures on AuthnRequests.\n\nTests use webmock to stub out the endpoint that serves metadata and to\ncheck that the right requests are made. Webmock is started on a dynamic\nport to avoid conflicts with other processes.\n\nWe considered using @ClassRules for both starting webmock and starting\nthe dropwizard application in the BridgeApplicationIntegrationTest. But\nthis would be confusing, because in the test the code we're testing is\nthe application startup itself (which should make a request for\nmetadata). To make it clearer what's going on we've switched to using\nmanual @Before and @After methods to start and stop webmock and we've\nmanually started the dropwizard application in the test method itself\n(since application startup is the code under test).\n\nAuthors: @chrisholmes @richardtowers @niyioyelade","distinct":true,"url":"https://api.github.com/repos/alphagov/verify-eidas-bridge/commits/ad2f1298adc995d5d5e17f784f24a14a8636da7e"},{"sha":"d68e426954ca3a5ce4937165715c6d1656fb71a8","author":{"name":"Oyeniyi Oyelade","email":"c552d33fed7ba584ecb120bf752d34d109b1df45@yahoo.com"},"message":"5222: Add endpoint to receive AuthnRequests\n\nMost of the handling of AuthnRequests has been pulled into a helper\nclass, which is lightly covered by unit tests. There are AppRule tests\nthat post AuthnRequests with valid and invalid signatures to check that\nit is being validated correctly.\n\nSince many tests are likely to want Metadata without necessarily caring\nabout the fact it's requested or the exact payload we've created a\nMetadataRule that sets up wiremock with sensible defaults for Metadata.\n\nNeed to ensure Authn Request is being signed with the right Cert.\nNeed to write Code to validate signature on the Authn Request.\nNeed to ensure the call to metadata on startup is working okay\n\nAuthors: @niyioyelade @richardtowers","distinct":true,"url":"https://api.github.com/repos/alphagov/verify-eidas-bridge/commits/d68e426954ca3a5ce4937165715c6d1656fb71a8"},{"sha":"7e483d81671cdc451176301952afe6935f4778f4","author":{"name":"Richard Towers","email":"6b5abcb5e5058fa0940d16fafc2b224ff0955dd8@digital.cabinet-office.gov.uk"},"message":"5222: Wire up bridge to work with compliance tool\n\nAdds a script to initialize the Verify Compliance tool (hosted on our\nreference environment) to point at a locally running instance of the\nbridge. Changes the bridge to start on a port that doesn't conflict with\nTomcat (or any of the Verify microservices).\n\nAlso adds validation of the AuthnRequest Issuer (which has to be hub).\n\nAlso removes a dependency on hub-saml-test-utils (which was basically\njust making a simple constructor call).\n\nAuthors: @richardtowers @suneetkamath","distinct":true,"url":"https://api.github.com/repos/alphagov/verify-eidas-bridge/commits/7e483d81671cdc451176301952afe6935f4778f4"},{"sha":"1268db7bd3f6fe56defb312aa25bb22cd8d4bf1d","author":{"name":"Richard Towers","email":"6b5abcb5e5058fa0940d16fafc2b224ff0955dd8@digital.cabinet-office.gov.uk"},"message":"5223: Get metadata from eIDAS as well as Verify\n\nWe need to have metadata from the eIDAS connector node so that we know\nwhere to forward the AuthnRequest to.\n\nAuthors: @richardtowers @suneetkamath","distinct":true,"url":"https://api.github.com/repos/alphagov/verify-eidas-bridge/commits/1268db7bd3f6fe56defb312aa25bb22cd8d4bf1d"},{"sha":"09ea464833c86f2b59a7d6e9a39c037d902d0f08","author":{"name":"Suneet Kamath","email":"7246ef0948419a53e8907487bca90a864349d310@digital.cabinet-office.gov.uk"},"message":"5223 :  configured bridge to point to EIDAS connector node metadata\n\nAdded a truststore with connector node CA certs\n\nAuthors: @richardtowers @suneetkamath","distinct":true,"url":"https://api.github.com/repos/alphagov/verify-eidas-bridge/commits/09ea464833c86f2b59a7d6e9a39c037d902d0f08"},{"sha":"e01ce7787384619953c2a27d7fdbb0fe9d67dbe5","author":{"name":"Richard Towers","email":"6b5abcb5e5058fa0940d16fafc2b224ff0955dd8@digital.cabinet-office.gov.uk"},"message":"5223: Create a resource to submit AuthnRequests to the Connector Node\n\nFor now we're just passing the ID of the incoming SAML request in the\nURL, because this needs to be the same in the message we send to the\nconnector node. Later this will want to go in the user's session (at the\nmoment the plan is for this to be a JWT).\n\nAdded AppRule test for the new resource and unit tests for the\nEidasAuthnRequestGenerator.\n\nTODO: all the rest of the AuthnRequest.\n\nAuthors: @richardtowers @suneetkamath","distinct":true,"url":"https://api.github.com/repos/alphagov/verify-eidas-bridge/commits/e01ce7787384619953c2a27d7fdbb0fe9d67dbe5"},{"sha":"1253a8a501cecb9c440bdfeb49b3d0e6316a91f2","author":{"name":"Richard Towers","email":"6b5abcb5e5058fa0940d16fafc2b224ff0955dd8@digital.cabinet-office.gov.uk"},"message":"5223: WIP generate authnrequest\n\nAuthors: @richardtowers @suneetkamath","distinct":true,"url":"https://api.github.com/repos/alphagov/verify-eidas-bridge/commits/1253a8a501cecb9c440bdfeb49b3d0e6316a91f2"},{"sha":"979a544624fc7f9fe770aa65bbc7b2cf3ab01c2a","author":{"name":"Richard Towers","email":"6b5abcb5e5058fa0940d16fafc2b224ff0955dd8@digital.cabinet-office.gov.uk"},"message":"5223: Add NameIDPolicy, RequestedAuthnContext and Extensions\n\nTo the AuthnRequest. Note that the extensions are missing the requested\nattributes at the moment.\n\nAuthors: @richardtowers @sfkamath","distinct":true,"url":"https://api.github.com/repos/alphagov/verify-eidas-bridge/commits/979a544624fc7f9fe770aa65bbc7b2cf3ab01c2a"},{"sha":"aef19a91a0384670830c3c0da2fd0818f99c0777","author":{"name":"Richard Towers","email":"6b5abcb5e5058fa0940d16fafc2b224ff0955dd8@digital.cabinet-office.gov.uk"},"message":"5223: Build our own RequestedAttribute implementation\n\nEidas add some SAML extensions which need to be marshalled to and from\nXML. There's a RequestedAttribute element which is similar to a\nAttribute from opensaml core, but adds an isRequired attribute. This\ncommit adds the implementation of the opensaml classes needed to\nrepresent, marshal, and unmarshal these elements.\n\nWe've also put the eidas XML Namespace on the root AuthnRequest element\nRather than declaring it where it's first used. This is neater, and it\nmakes the AuthnRequest slightly smaller because we don't have to declare\nthe namespace multiple times.\n\nAuthors: @richardtowers @sfkamath","distinct":true,"url":"https://api.github.com/repos/alphagov/verify-eidas-bridge/commits/aef19a91a0384670830c3c0da2fd0818f99c0777"},{"sha":"848fe2a4fcc75fc6fc3628eb037f3705fff27c43","author":{"name":"Richard Towers","email":"6b5abcb5e5058fa0940d16fafc2b224ff0955dd8@digital.cabinet-office.gov.uk"},"message":"5223: Sign Eidas AuthnRequests, set issuer to metadata URI\n\nThe keystore containing the signing key will be provided as a base64\nencoded byte array in the configuration.\n\nWe've also changed the issuer to be the URL of our metadata, because it\nseems that this is the thing eIDAS uses to fetch metadata and thus check\nthe signature on the AuthnRequest.\n\nTo check the signature in the integration tests we need to dynamically\nbuild a keystore (see TestSigningKeyStoreProvider), which is quite\ncomplex.\n\nAuthors: @richardtowers @sfkamath @chrisholmes","distinct":true,"url":"https://api.github.com/repos/alphagov/verify-eidas-bridge/commits/848fe2a4fcc75fc6fc3628eb037f3705fff27c43"},{"sha":"86bb9ede489efe97d3743f6c17ef0be8b6a29bfe","author":{"name":"Richard Towers","email":"6b5abcb5e5058fa0940d16fafc2b224ff0955dd8@digital.cabinet-office.gov.uk"},"message":"5223: Add singleSignOnLocation and submit button to SAML form\n\nThis will allow us to POST the SAML to the eidas connector node.\nSingleSignOnServiceLocation is pulled from the eidas metadata.\n\nAlso did some refatoring of the MetadataRule (you now need one for\nverify and one for eidas) and the VerifyEidasBridgeFactory (which is now\nmore careful about returning the same instances each time).\n\nAuthors: @richardtowers @sfkamath @chrisholmes","distinct":true,"url":"https://api.github.com/repos/alphagov/verify-eidas-bridge/commits/86bb9ede489efe97d3743f6c17ef0be8b6a29bfe"}]}
{"actor":{"display_login":"richardTowers"}}