On 2019-09-23 23:09, Scott Koranda wrote:
Hi,
I am using today's pyFF master head, commit
bbdf245ccdb0be8ce45dda8c0cef06a6d33e2755
My pipeline contains
- when request:
- select:
- pipe:
- when accept application/xml:
- first
- finalize:
cacheDuration: PT12H
validUntil: P10D
- sign:
key: metadata-signer.key
cert: metadata-signer.crt
- emit application/xml
- break
- when accept application/json:
- discojson
- emit application/json
- break
This query returns the XML I expect
curl 'http://127.0.0.1:8080/entities/https%3A%2F%2Fwiki.ligo.org%2Fshibboleth-sp
proving that pyFF has the metadata for the entityID.
But this query returns an empty <EntitiesDescriptor>:
curl
'http://127.0.0.1:8080/entities/%7Bsha1%7Dff767393c6b06e8282603e9e4541ac1e878d63aa
Note that
$ python3
Python 3.7.3 (default, Apr 3 2019, 05:39:12)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license"
for more information.
>> from hashlib import sha1
>> m = sha1()
>>
m.update(b'https://wiki.ligo.org/shibboleth-sp')
>> m.hexdigest()
'ff767393c6b06e8282603e9e4541ac1e878d63aa'
This is problematic since thiss-js wants to use sha1 hashes to query
MDQ.
Is there something special I have to configure to get pyFF to accept the
sha1 hash?
No you shouldn't have to do anything. I got a lot of PRs from the
hackathon today. Let me work through those tomorrow and then get
this issue fixed. It is certainly not expected.
Cheers Leif
Thanks,
Scott K
_______________________________________________
Idpy-discuss mailing list
Idpy-discuss at lists.sunet.se
https://lists.sunet.se/listinfo/idpy-discuss
to query
MDQ.
Is there something special I have to configure to get pyFF to accept the
sha1 hash?
Thanks,
Scott K
_______________________________________________
Idpy-discuss mailing list
Idpy-discuss at lists.sunet.se
https://lists.sunet.se/listinfo/idpy-discuss