You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@syncope.apache.org by Colm O hEigeartaigh <co...@apache.org> on 2012/09/20 17:39:35 UTC
Certificates in Syncope
Hi all,
If I'm not mistaken, the ability to support binary attributes as defined in
SYNCOPE-123 will give the ability to import user Certificates as an
Attribute in Syncope. So for example if you are importing users from an
LDAP backend, you could map the inetOrgPerson userCertificate attribute to
a local binary attribute in Syncope.
The question is whether we should consider Certificates as a special kind
of User Attribute in Syncope rather than just a binary attribute? Maybe the
Subject DN of the certificate would be displayed on the console for
example, or the PEM format of the certificate could be displayed for
copying+pasting. Perhaps the REST interface could also give special access
to X509Certificates?
Just some thoughts, I appreciate any feedback!
Colm.
--
Colm O hEigeartaigh
Talend Community Coder
http://coders.talend.com
Re: Usage of Change Log Column (Sync)
Posted by Francesco Chicchiriccò <il...@apache.org>.
Denis,
please start a new thread instead of replying to old e-mails, otherwise
our ML archives will go crazy.
Thanks!
Regards.
On 12/10/2012 16:08, Denis Signoretto wrote:
> Hi Everybody,
> in the ConnId DB Table Connector there is a field named " Change Log
> Column (Sync)".
> Can you give me some details how it's used by Syncope?
> Thanks,
> Denis.
--
Francesco Chicchiriccò
ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member
http://people.apache.org/~ilgrosso/
Usage of Change Log Column (Sync)
Posted by Denis Signoretto <de...@intesys.it>.
Hi Everybody,
in the ConnId DB Table Connector there is a field named " Change Log Column (Sync)".
Can you give me some details how it's used by Syncope?
Thanks,
Denis.
Re: Certificates in Syncope
Posted by Francesco Chicchiriccò <il...@apache.org>.
On 24/09/2012 12:34, Colm O hEigeartaigh wrote:
> Hi Francesco,
>
> > Why not imagine that when defining a Binary attribute schema you will
> > need to provide the mime-type?
> > There could be a pluggable list of supported mime types with associated
> > features: for X509Certificates get DN and PEM, for image/jpeg get width
> > and height, and so on.
>
> This sounds like a good idea to me. The list of supported mime types
> should be pluggable but should also have a "default" setting of some
> common mime types. Just to clarify, are the "associated features" for
> display purposes only in the console, or could they be useful in some
> other way?
Hi Colm,
I am only brainstorming here :-)
Anyway, I think it is worth to say that the admin console has always
been a "REST client like the others", so I would keep up with this line.
Regards.
> On Thu, Sep 20, 2012 at 5:02 PM, Francesco Chicchiriccò
> <ilgrosso@apache.org <ma...@apache.org>> wrote:
>
> On 20/09/2012 17:39, Colm O hEigeartaigh wrote:
> > Hi all,
> >
> > If I'm not mistaken, the ability to support binary attributes as
> > defined in SYNCOPE-123 will give the ability to import user
> > Certificates as an Attribute in Syncope. So for example if you are
> > importing users from an LDAP backend, you could map the
> inetOrgPerson
> > userCertificate attribute to a local binary attribute in Syncope.
> >
> > The question is whether we should consider Certificates as a special
> > kind of User Attribute in Syncope rather than just a binary
> attribute?
> > Maybe the Subject DN of the certificate would be displayed on the
> > console for example, or the PEM format of the certificate could be
> > displayed for copying+pasting. Perhaps the REST interface could also
> > give special access to X509Certificates?
> >
> > Just some thoughts, I appreciate any feedback!
>
> Hi Colm,
> very nice to start discussing about this! I've added a reference
> to this
> mail thread to SYNCOPE-123.
>
> What you say above about certificates is perfectly reasonable; what
> about images, PDF files, or any other kind of binary data?
> We may think to implement an extensible mime-type handling mechanism.
>
> Let's consider some examples of attribute schema definition: for Date
> you need to provide the conversion pattern (from / to String), for
> Enum
> you need to provide the enumeration labels and values.
> Why not imagine that when defining a Binary attribute schema you will
> need to provide the mime-type?
>
> There could be a pluggable list of supported mime types with
> associated
> features: for X509Certificates get DN and PEM, for image/jpeg get
> width
> and height, and so on.
>
> WDYT?
>
--
Francesco Chicchiriccò
ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member
http://people.apache.org/~ilgrosso/
Re: Certificates in Syncope
Posted by Colm O hEigeartaigh <co...@apache.org>.
Hi Francesco,
> Why not imagine that when defining a Binary attribute schema you will
> need to provide the mime-type?
> There could be a pluggable list of supported mime types with associated
> features: for X509Certificates get DN and PEM, for image/jpeg get width
> and height, and so on.
This sounds like a good idea to me. The list of supported mime types should
be pluggable but should also have a "default" setting of some common mime
types. Just to clarify, are the "associated features" for display purposes
only in the console, or could they be useful in some other way?
Colm.
On Thu, Sep 20, 2012 at 5:02 PM, Francesco Chicchiriccò <ilgrosso@apache.org
> wrote:
> On 20/09/2012 17:39, Colm O hEigeartaigh wrote:
> > Hi all,
> >
> > If I'm not mistaken, the ability to support binary attributes as
> > defined in SYNCOPE-123 will give the ability to import user
> > Certificates as an Attribute in Syncope. So for example if you are
> > importing users from an LDAP backend, you could map the inetOrgPerson
> > userCertificate attribute to a local binary attribute in Syncope.
> >
> > The question is whether we should consider Certificates as a special
> > kind of User Attribute in Syncope rather than just a binary attribute?
> > Maybe the Subject DN of the certificate would be displayed on the
> > console for example, or the PEM format of the certificate could be
> > displayed for copying+pasting. Perhaps the REST interface could also
> > give special access to X509Certificates?
> >
> > Just some thoughts, I appreciate any feedback!
>
> Hi Colm,
> very nice to start discussing about this! I've added a reference to this
> mail thread to SYNCOPE-123.
>
> What you say above about certificates is perfectly reasonable; what
> about images, PDF files, or any other kind of binary data?
> We may think to implement an extensible mime-type handling mechanism.
>
> Let's consider some examples of attribute schema definition: for Date
> you need to provide the conversion pattern (from / to String), for Enum
> you need to provide the enumeration labels and values.
> Why not imagine that when defining a Binary attribute schema you will
> need to provide the mime-type?
>
> There could be a pluggable list of supported mime types with associated
> features: for X509Certificates get DN and PEM, for image/jpeg get width
> and height, and so on.
>
> WDYT?
>
> --
> Francesco Chicchiriccò
>
> ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member
> http://people.apache.org/~ilgrosso/
>
>
--
Colm O hEigeartaigh
Talend Community Coder
http://coders.talend.com
Re: Certificates in Syncope
Posted by Francesco Chicchiriccò <il...@apache.org>.
On 20/09/2012 17:39, Colm O hEigeartaigh wrote:
> Hi all,
>
> If I'm not mistaken, the ability to support binary attributes as
> defined in SYNCOPE-123 will give the ability to import user
> Certificates as an Attribute in Syncope. So for example if you are
> importing users from an LDAP backend, you could map the inetOrgPerson
> userCertificate attribute to a local binary attribute in Syncope.
>
> The question is whether we should consider Certificates as a special
> kind of User Attribute in Syncope rather than just a binary attribute?
> Maybe the Subject DN of the certificate would be displayed on the
> console for example, or the PEM format of the certificate could be
> displayed for copying+pasting. Perhaps the REST interface could also
> give special access to X509Certificates?
>
> Just some thoughts, I appreciate any feedback!
Hi Colm,
very nice to start discussing about this! I've added a reference to this
mail thread to SYNCOPE-123.
What you say above about certificates is perfectly reasonable; what
about images, PDF files, or any other kind of binary data?
We may think to implement an extensible mime-type handling mechanism.
Let's consider some examples of attribute schema definition: for Date
you need to provide the conversion pattern (from / to String), for Enum
you need to provide the enumeration labels and values.
Why not imagine that when defining a Binary attribute schema you will
need to provide the mime-type?
There could be a pluggable list of supported mime types with associated
features: for X509Certificates get DN and PEM, for image/jpeg get width
and height, and so on.
WDYT?
--
Francesco Chicchiriccò
ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member
http://people.apache.org/~ilgrosso/