The Fedvis acceptance test environment is accessible only to members of Fedvis. All member metadata published in the Fedvis aggregated metadata feed is by confirmed member organizations, that must comply with Fedvis trust framework and technical requirements.
Access to Fedvis acceptance test environment
All members of Fedvis gain automatic access to the acceptance test environment. On finalization of membership, all Technical Contacts can access Federationsadmin by using their e-identification (BankID or Freja eID+). Technical Contacts also have the ability to create Technical Agents to delegate access to the member's metadata management
Uploading metadata to Fedvis
Uploading metadata in Federationsadmin
To upload metadata to Fedvis, log on to Federationsadmin with your e-identification (BankID or Freja eID+).
Note: You must be either the member's Technical Contact or Technical Agent to gain access.
Log on to Fedvis acceptance test in Federationsadmin
Technical information
Metadata
Metadata for Fedvis acceptance test is found below.
https://fed.fedvis.se/accept/md/metadata.xml
Public key for verifying signature of federation metadata is found below.
-----BEGIN CERTIFICATE----- MIIFxTCCA62gAwIBAgIUOzUhMH9lGnTxeR9v1AQ2I7NYt4IwDQYJKoZIhvcNAQEL BQAwcTEUMBIGA1UEAwwLU0FNTC1zaWduZXIxKDAmBgNVBAoMH1RoZSBTd2VkaXNo IEludGVybmV0IEZvdW5kYXRpb24xGzAZBgNVBAsMEkZlZGVyYXRlZCBTZXJ2aWNl czESMBAGA1UEBwwJU3RvY2tob2xtMCAXDTIzMDkxODEyNDI0NVoYDzIxMjMwODI1 MTI0MjQ1WjBxMRQwEgYDVQQDDAtTQU1MLXNpZ25lcjEoMCYGA1UECgwfVGhlIFN3 ZWRpc2ggSW50ZXJuZXQgRm91bmRhdGlvbjEbMBkGA1UECwwSRmVkZXJhdGVkIFNl cnZpY2VzMRIwEAYDVQQHDAlTdG9ja2hvbG0wggIiMA0GCSqGSIb3DQEBAQUAA4IC DwAwggIKAoICAQDQQh8F4KvzuSoYOB3aNlAD0/wFgE6TXi4imToa4nBP41p+Y4nP SMjLAgzL8FRUJ0utAOFeLqMq/fndXORZW7Xl/wmlGCJx2+xfyYgdT4+wQghbPV0M 4zmKyWunl5N84A5DrhPltoCTVS6I3ucAgpzMh132y9YnM88MW4+EuTt3+oRXstA8 fpJ3xIX3x0DUDk59eH/0FQwALrK3CkY5xcb1FBAqFAQgw/mU6V1zyZIQ+Qz3iL5A kWV2yeCKstz4qWbNnGGxSBq3JnPUcoWLs9QJOTxTHqK4f40ZXqeOjPKxmY7q+2LP BAe9xvP08y2M8d78+fll1aqQRJc3D8jd9WEwPuMf8Dqs//Nfk7UC3Gl7wjqQArKz fY9poeEY2WwNMOsfnmtFlO3yCZzvLgWXbil6afzSKBjIZZuoyuKWAzZV+PJgzwWd BnTxbZxw91lXWZzus1EUL9W89P25cHoZVlDWIMoidDDv8BEGZ5Uk6J4BejHcADpg 8ab7dL8CEz2LppVnQKQNjHoatQji74KF8nPIppGbasVaCJlugaOY02MmVYo32T6l 3Dxtc4cCAdEXjVfWvhcRTu4A9qqIYaAIeG5zJ88nyeynW1NIzyDyI1VYMqypsTKt MHcsx2DMTR+M3+EEN340JfvkcjN6BbRTW6IispFBDAIIzwxdbzjNlm+6XwIDAQAB o1MwUTAdBgNVHQ4EFgQUOfgCEzWuxk5w2v0uSY97ydRDasQwHwYDVR0jBBgwFoAU OfgCEzWuxk5w2v0uSY97ydRDasQwDwYDVR0TAQH/BAUwAwEB/zANBgkqhkiG9w0B AQsFAAOCAgEAKQm/y1SxXPT1wk5nhmMgwtLYpq5OrASrH1fhVV8cli9Mf1PmOvHW UfishBZmFO53IaxJRS12PyDdWIzzO0L/XWIST5HPGWV7i2VcXWG9yyVBNar2maRX OA5VaNVjMW0UMxo3udkm7QBqsiJ1wOzTwyEQLHyJgB7td1/ikVrUC8joknyBH9wX p4GtdRe9gbykDpLWp6Oi96/hr8NrCQE8CP+inXUGLSYv35DOmalbi77MD0leLVzw OGOLApuqgoL/RoXvYN30slABCdPBTml03Ylhhz/+GY4sy04a+8cgXeMadvBGB/S6 mh89egIDkTYpqg4WPVuGcmZNU+qBzKc5mdr5Y/Fcv1dbwJanUDLXW8OasRhSsaGP p7G6vSWP3Myke1GqV0eonvN3unvnFURndOi01zFd9IbGfQTZbzkM4QbSRrO7zeqR vpEQDlEFIuWaVuKjsgzED3Pf9znTNOXgRg7CR2yRQYyY3SCVEaowKrEJUvNVCeMN gXnFVx5tPUZIn612cpPVundlVnEgvtzmP9lHir2LyTMgHrbIPVHegTUtR8V+WEVz vCF7w/2eNqaBkslG8syDz9QxQH1EE/Gl0wuWWHYFz9NGf7kBYKsGrlFM5D5uibRd lhJ8whmDQfNiP9pLpm3Mjz4b6/CuBOWD9ImRepBqraKNo0JM5l0zj48= -----END CERTIFICATE-----
SHA 256 fingerprint: 55:B2:D1:B2:D1:65:2B:D2:F4:A0:1F:DA:9A:E2:45:57:A8:CF:D4:6A:9E:40:1C:F5:57:43:A0:E8:6B:8E:E3:58
Verify metadata with certificate
We recommend verifying the fingerprint of the signing certificate with the federation operator before adding the certificate to your IdP/SP trust. After trusting the certificate, always verify federation metadata signature with signing certificate to guarantee metadata integrity.
0 Comments