shibboleth-dev - Re: storedID column sizes
Subject: Shibboleth Developers
List archive
- From: Lukas Haemmerle <>
- To:
- Subject: Re: storedID column sizes
- Date: Mon, 17 Mar 2008 15:07:03 +0100
- Organization: SWITCH - Serving Swiss Universities
Will Norris wrote:
I was updating the wiki page for the StoredID DC[0] and noticed the varchar columns have no size. Was this deliberate? Should we at least be recommending sizes?
I just added an example for MySQL on the wiki page before I read this post :)
My initial thoughts:
localEntity varchar(1024) - per SAML2 spec, entity ID must be limited to 1024 characters
At least for MySQL the max for varchar is 255. One then would have to use TEXT as type for this I assume.
peerEntity varchar(1024) - see localEntity
same here
principalName varchar(?)
255 should be more than fine
localId varchar(?)
same here
persistentId(36) - old hash algorithm produced 28 character string, new algorithm creates 36 character guid
Sounds reasonable.
peerProvidedId(?)
No idea what could be reasonable for this.
Lukas
--
SWITCH
Serving Swiss Universities
--------------------------
Lukas Haemmerle, Software Engineer, Security
Werdstrasse 2, P.O. Box, 8021 Zurich, Switzerland
phone +41 44 268 15 64, fax +41 44 268 15 68
,
http://www.switch.ch
- storedID column sizes, Will Norris, 03/14/2008
- Re: storedID column sizes, Lukas Haemmerle, 03/17/2008
Archive powered by MHonArc 2.6.16.