Re: [pylons-discuss] REF. FORMULARIOS E VALIDAÇÃO (PYRAMID)

[Oberdan Santos]

Foi o que imaginei. Obrigado 

Em sex., 17 de nov. de 2023 às 19:31, Laurent Daverio 
escreveu:

> You can't integrate react-hook-form and yup with Pyramid(*), these are
> frontend components. If your goal is to write a simple Pyramid app to get
> started, don't use them yet, stick to a classic architecture with the
> Python / Pyramid ecosystem.
>
>
>
> Le ven. 17 nov. 2023 à 22:41, Oberdan Santos  a
> écrit :
>
>> Vejo que ainda há algumas pendencias a  serem resolvidas no Deform. Vi
>> que o  REACT HOOK FORM + YUP é um boa solução para formularios e
>> validações. No entanto, estou receioso quanto ao processo de integração
>> dessas bibliotecas. Para evitar problemas na aplicação PYRAMID devo
>> instalar o NODES  para suporte a essas  bibliotecas ou há algum outro
>> procedimento. Caso tenha algum link de tutotial ou qualquer outro apoio,
>> por gentileza envie.
>>
>> Desde já agradeço
>>
>> Em sexta-feira, 17 de novembro de 2023 às 17:42:56 UTC-3, Steve Piercy
>> escreveu:
>>
>>> Deform has had a flurry of activity over the last couple of weeks to
>>> update the widgets to use Bootstrap 5.3. I hope to have time this weekend
>>> to make an alpha release, 3.0.0a.
>>>
>>> https://github.com/Pylons/deform/pull/529
>>>
>>> --steve
>>>
>>>
>>> On 11/17/23 7:31 AM, Laurent Daverio wrote:
>>>
>>> Hello,
>>>
>>> Deform has a big problem, it generates widgets for Bootstrap 3. I had
>>> patched mine it to make it compatible with Bootstrap 4, but now the
>>> standard version is Bootstrap 5. And I've switched to React and Material UI
>>> anyway. In retrospect, I think it's not a good idea to use a library which
>>> binds validation and widgets.
>>>
>>> As regards validation itself, I started with Colander, it was
>>> complicated but worked. Then I used "schema" for a few months. Now I've
>>> seen the light and I use Pydantic. I wonder why I used anything else in the
>>> past... Coming from FastAPI, I believe you must be familiar with Pydantic.
>>>
>>> In case you need frontend validation too, you can have a look at Yup,
>>> it"s a bit like "schema", but for Javascript. Unfortunately, there is no
>>> equivalent to Pydantic...
>>>
>>> Laurent.
>>>
>>> Le ven. 17 nov. 2023 à 16:13, Oberdan Santos  a
>>> écrit :
>>>
 Olá!!   Gostaria de saber se todos têm adotado o DEFORM como biblioteca
 padrão para formulario e validação  ou outras bibliotecas de uso facil com
 o Pyramid ?

 Oberdan costa


 --
 You received this message because you are subscribed to the Google
 Groups "pylons-discuss" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to pylons-discus...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/pylons-discuss/f86a52d6-171d-4097-b595-4e3718105d74n%40googlegroups.com
 
 .

>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "pylons-discuss" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to pylons-discus...@googlegroups.com.
>>>
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/pylons-discuss/CAB7cU6xPpeo_mUBjTC9obqZiRXcm40qhco%2Bk%2BnDSvCHmjn8eoQ%40mail.gmail.com
>>> 
>>> .
>>>
>>>
>>> --
>> You received this message because you are subscribed to the Google Groups
>> "pylons-discuss" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to pylons-discuss+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/pylons-discuss/1a475df5-b563-4ff1-afd2-f5a9de737460n%40googlegroups.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "pylons-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pylons-discuss+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/pylons-discuss/CAB7cU6zOeuUhYJiq4ZUqapB1Os-Rog2wE8wfeim29tj5sw%2BU4Q%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

Re: [pylons-discuss] REF. FORMULARIOS E VALIDAÇÃO (PYRAMID)

[Laurent Daverio]

You can't integrate react-hook-form and yup with Pyramid(*), these are
frontend components. If your goal is to write a simple Pyramid app to get
started, don't use them yet, stick to a classic architecture with the
Python / Pyramid ecosystem.



Le ven. 17 nov. 2023 à 22:41, Oberdan Santos  a
écrit :

> Vejo que ainda há algumas pendencias a  serem resolvidas no Deform. Vi que
> o  REACT HOOK FORM + YUP é um boa solução para formularios e validações. No
> entanto, estou receioso quanto ao processo de integração dessas
> bibliotecas. Para evitar problemas na aplicação PYRAMID devo instalar o
> NODES  para suporte a essas  bibliotecas ou há algum outro procedimento.
> Caso tenha algum link de tutotial ou qualquer outro apoio, por gentileza
> envie.
>
> Desde já agradeço
>
> Em sexta-feira, 17 de novembro de 2023 às 17:42:56 UTC-3, Steve Piercy
> escreveu:
>
>> Deform has had a flurry of activity over the last couple of weeks to
>> update the widgets to use Bootstrap 5.3. I hope to have time this weekend
>> to make an alpha release, 3.0.0a.
>>
>> https://github.com/Pylons/deform/pull/529
>>
>> --steve
>>
>>
>> On 11/17/23 7:31 AM, Laurent Daverio wrote:
>>
>> Hello,
>>
>> Deform has a big problem, it generates widgets for Bootstrap 3. I had
>> patched mine it to make it compatible with Bootstrap 4, but now the
>> standard version is Bootstrap 5. And I've switched to React and Material UI
>> anyway. In retrospect, I think it's not a good idea to use a library which
>> binds validation and widgets.
>>
>> As regards validation itself, I started with Colander, it was complicated
>> but worked. Then I used "schema" for a few months. Now I've seen the light
>> and I use Pydantic. I wonder why I used anything else in the past... Coming
>> from FastAPI, I believe you must be familiar with Pydantic.
>>
>> In case you need frontend validation too, you can have a look at Yup,
>> it"s a bit like "schema", but for Javascript. Unfortunately, there is no
>> equivalent to Pydantic...
>>
>> Laurent.
>>
>> Le ven. 17 nov. 2023 à 16:13, Oberdan Santos  a
>> écrit :
>>
>>> Olá!!   Gostaria de saber se todos têm adotado o DEFORM como biblioteca
>>> padrão para formulario e validação  ou outras bibliotecas de uso facil com
>>> o Pyramid ?
>>>
>>> Oberdan costa
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "pylons-discuss" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to pylons-discus...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/pylons-discuss/f86a52d6-171d-4097-b595-4e3718105d74n%40googlegroups.com
>>> 
>>> .
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "pylons-discuss" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to pylons-discus...@googlegroups.com.
>>
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/pylons-discuss/CAB7cU6xPpeo_mUBjTC9obqZiRXcm40qhco%2Bk%2BnDSvCHmjn8eoQ%40mail.gmail.com
>> 
>> .
>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "pylons-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pylons-discuss+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/pylons-discuss/1a475df5-b563-4ff1-afd2-f5a9de737460n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pylons-discuss/CAB7cU6zOeuUhYJiq4ZUqapB1Os-Rog2wE8wfeim29tj5sw%2BU4Q%40mail.gmail.com.

Re: [pylons-discuss] REF. FORMULARIOS E VALIDAÇÃO (PYRAMID)

[Oberdan Santos]

Vejo que ainda há algumas pendencias a  serem resolvidas no Deform. Vi que 
o  REACT HOOK FORM + YUP é um boa solução para formularios e validações. No 
entanto, estou receioso quanto ao processo de integração dessas 
bibliotecas. Para evitar problemas na aplicação PYRAMID devo instalar o 
NODES  para suporte a essas  bibliotecas ou há algum outro procedimento. 
Caso tenha algum link de tutotial ou qualquer outro apoio, por gentileza 
envie.

Desde já agradeço

Em sexta-feira, 17 de novembro de 2023 às 17:42:56 UTC-3, Steve Piercy 
escreveu:

> Deform has had a flurry of activity over the last couple of weeks to 
> update the widgets to use Bootstrap 5.3. I hope to have time this weekend 
> to make an alpha release, 3.0.0a.
>
> https://github.com/Pylons/deform/pull/529
>
> --steve
>
>
> On 11/17/23 7:31 AM, Laurent Daverio wrote:
>
> Hello,
>
> Deform has a big problem, it generates widgets for Bootstrap 3. I had 
> patched mine it to make it compatible with Bootstrap 4, but now the 
> standard version is Bootstrap 5. And I've switched to React and Material UI 
> anyway. In retrospect, I think it's not a good idea to use a library which 
> binds validation and widgets.
>
> As regards validation itself, I started with Colander, it was complicated 
> but worked. Then I used "schema" for a few months. Now I've seen the light 
> and I use Pydantic. I wonder why I used anything else in the past... Coming 
> from FastAPI, I believe you must be familiar with Pydantic.
>
> In case you need frontend validation too, you can have a look at Yup, it"s 
> a bit like "schema", but for Javascript. Unfortunately, there is no 
> equivalent to Pydantic...
>
> Laurent.
>
> Le ven. 17 nov. 2023 à 16:13, Oberdan Santos  a 
> écrit :
>
>> Olá!!   Gostaria de saber se todos têm adotado o DEFORM como biblioteca 
>> padrão para formulario e validação  ou outras bibliotecas de uso facil com 
>> o Pyramid ? 
>>
>> Oberdan costa
>>
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "pylons-discuss" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to pylons-discus...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/pylons-discuss/f86a52d6-171d-4097-b595-4e3718105d74n%40googlegroups.com
>>  
>> 
>> .
>>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "pylons-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to pylons-discus...@googlegroups.com.
>
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/pylons-discuss/CAB7cU6xPpeo_mUBjTC9obqZiRXcm40qhco%2Bk%2BnDSvCHmjn8eoQ%40mail.gmail.com
>  
> 
> .
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pylons-discuss/1a475df5-b563-4ff1-afd2-f5a9de737460n%40googlegroups.com.

Re: [pylons-discuss] REF. FORMULARIOS E VALIDAÇÃO (PYRAMID)

[Steve Piercy]

Deform has had a flurry of activity over the last couple of weeks to update the 
widgets to use Bootstrap 5.3. I hope to have time this weekend to make an alpha 
release, 3.0.0a.

https://github.com/Pylons/deform/pull/529

--steve


On 11/17/23 7:31 AM, Laurent Daverio wrote:

Hello,

Deform has a big problem, it generates widgets for Bootstrap 3. I had patched 
mine it to make it compatible with Bootstrap 4, but now the standard version is 
Bootstrap 5. And I've switched to React and Material UI anyway. In retrospect, 
I think it's not a good idea to use a library which binds validation and 
widgets.

As regards validation itself, I started with Colander, it was complicated but worked. 
Then I used "schema" for a few months. Now I've seen the light and I use 
Pydantic. I wonder why I used anything else in the past... Coming from FastAPI, I believe 
you must be familiar with Pydantic.

In case you need frontend validation too, you can have a look at Yup, it"s a bit like 
"schema", but for Javascript. Unfortunately, there is no equivalent to Pydantic...

Laurent.

Le ven. 17 nov. 2023 à 16:13, Oberdan Santos  a écrit :

Olá!!  Gostaria de saber se todos têm adotado o DEFORM como biblioteca 
padrão para formulario e validação  ou outras bibliotecas de uso facil com o 
Pyramid ?

Oberdan costa


-- 
You received this message because you are subscribed to the Google Groups "pylons-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an 
email to pylons-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pylons-discuss/f86a52d6-171d-4097-b595-4e3718105d74n%40googlegroups.com
 
.

--
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pylons-discuss/CAB7cU6xPpeo_mUBjTC9obqZiRXcm40qhco%2Bk%2BnDSvCHmjn8eoQ%40mail.gmail.com
 
.


--
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pylons-discuss/1813eb70-6b60-40f2-8ca4-f3e209781387%40gmail.com.

Re: [pylons-discuss] Re: Using SSL client certificate in a Pyramid application

[Michael Merickel]

You don’t need a signed header. You just need to make sure your proxy is configured to remove that header from an incoming request and only put validated data into it before sending it to your app. This is standard for other headers set by your proxy as well. Definitely never trust a header without checking those properties of your deployment though. - MichaelOn Nov 17, 2023, at 10:02, Jonathan Vanasco  wrote:I do a lot of work with SSL Certs.  If you are using publicly trusted client certificates (i.e. LetsEncrypt, Digisign, etc), then you basically just need to do what Michael suggested - ensure your gateway or server populates the headers or environment variables with the information for the client.  Most implementations for that stuff will also insert a secret-signed header field to ensure the client did not try and stuff headers themselves.  You'd then need to validate the certificate again within python (see workaround #3 below)I think this is going to be a bit of a headache if you are using untrusted CAs for the client certificates (ie. you control the CA and allocate the certs to your clients/partners) and trying to implement the sort of policy that PostgreSQL and other systems offer with client verification.The complexity and level of work required come down to the following factors:* Who will issue the client certificates (a public trusted CA or your own private CA)* How much validation can you split between the gateway/server and Python (based on application design and business logic constraints), and where can the errors pop-up?If you are talking about custom CA certs, the two approaches I know of for this sort of stuff:1- (Easy for developer, harder for client) The client application stuffs the certificate into a header.  Everything happens as normal Pyramid app.  You just write pyramid code to require and validate the certificate header.  This isn't actually mTLS, but uses the client certificate similar to ssl keychains.2. (Hard for developer, easy for client) Actually use TLS Mutual Auth, which is what Theron first brought up.  With mTLS, the client certificate is presented and validated during the TLS handshake - which means you would need to configure the gateway or mod_wsgi to handle the validation.The large complexity of #2 is that many web servers / gateways can only be configured with a single client CA or a static client CA store - so building this as scalable to multiple clients may not necessarily be possible.The three workarounds I can think of are:1- Don't terminate TLS or validate the client certificate on the gateway, instead pass it all back to a python server like Waitress and see if you can handle everything via middleware to process the SSL connection.2- Terminate TLS on OpenResty(nginx) and use a Lua script to handle the client validation.  Then you can proxy that back to mod_wsgi.  I opensourced our dynamic SSL certificate tool for OpenResty here - https://github.com/aptise/lua-resty-peter_sslers - it does not do client certificates, but IMHO is a good reference for what you want to accomplish.    it looks like OpenResty has some builtin stuff for this, but if not - those are the correct hooks.  3- Terminate TLS on the gateway but make it very lax for the client certificate to pass - basically just checking to see if the certificate is valid and from the CA.  Then validate the client a second time in middleware/tween to ensure the certificate is active and allowed.  On Wednesday, November 15, 2023 at 9:13:39 AM UTC-5 Thierry Florac wrote:Hi,My problem is probably quite simple: I would like to be able, in a Pyramid application, to create a custom security policy which could use an SSL client certificate as a request credential to handle authentication (authorized certificates being referenced in a database or stored in a specific server directory).This application is then supposed to be published via mod_wsgi in an Apache server located behind an HAProxy.I tried to search here and there but didn't find any information about this...Any hint?Best regards,Thierry--   https://www.ulthar.net -- http://pyams.readthedocs.io




-- 
You received this message because you are subscribed to the Google Groups "pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/39f47b19-0e08-4936-aaff-3da5822dc90fn%40googlegroups.com.




-- 
You received this message because you are subscribed to the Google Groups "pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/F3D4E89A-A27F-4923-8ACA-DF1AF2B6821B%40gmail.com.

Re: [pylons-discuss] REF. FORMULARIOS E VALIDAÇÃO (PYRAMID)

[Oberdan Santos]

Perfeito!! Obrigado

Em sex., 17 de nov. de 2023 às 12:31, Laurent Daverio 
escreveu:

> Hello,
>
> Deform has a big problem, it generates widgets for Bootstrap 3. I had
> patched mine it to make it compatible with Bootstrap 4, but now the
> standard version is Bootstrap 5. And I've switched to React and Material UI
> anyway. In retrospect, I think it's not a good idea to use a library which
> binds validation and widgets.
>
> As regards validation itself, I started with Colander, it was complicated
> but worked. Then I used "schema" for a few months. Now I've seen the light
> and I use Pydantic. I wonder why I used anything else in the past... Coming
> from FastAPI, I believe you must be familiar with Pydantic.
>
> In case you need frontend validation too, you can have a look at Yup, it"s
> a bit like "schema", but for Javascript. Unfortunately, there is no
> equivalent to Pydantic...
>
> Laurent.
>
> Le ven. 17 nov. 2023 à 16:13, Oberdan Santos  a
> écrit :
>
>> Olá!!   Gostaria de saber se todos têm adotado o DEFORM como biblioteca
>> padrão para formulario e validação  ou outras bibliotecas de uso facil com
>> o Pyramid ?
>>
>> Oberdan costa
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "pylons-discuss" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to pylons-discuss+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/pylons-discuss/f86a52d6-171d-4097-b595-4e3718105d74n%40googlegroups.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "pylons-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pylons-discuss+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/pylons-discuss/CAB7cU6xPpeo_mUBjTC9obqZiRXcm40qhco%2Bk%2BnDSvCHmjn8eoQ%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pylons-discuss/CADST_G8HghvoARYKf5W1bvcDJk9XX%3D2uu6RKjin_zizxeOTDyg%40mail.gmail.com.

[pylons-discuss] Re: Using SSL client certificate in a Pyramid application

[Jonathan Vanasco]

I do a lot of work with SSL Certs.  If you are using publicly trusted 
client certificates (i.e. LetsEncrypt, Digisign, etc), then you basically 
just need to do what Michael suggested - ensure your gateway or server 
populates the headers or environment variables with the information for the 
client.  Most implementations for that stuff will also insert a 
secret-signed header field to ensure the client did not try and stuff 
headers themselves.  You'd then need to validate the certificate again 
within python (see workaround #3 below)

I think this is going to be a bit of a headache if you are using untrusted 
CAs for the client certificates (ie. you control the CA and allocate the 
certs to your clients/partners) and trying to implement the sort of policy 
that PostgreSQL and other systems offer with client verification.

The complexity and level of work required come down to the following 
factors:

* Who will issue the client certificates (a public trusted CA or your own 
private CA)
* How much validation can you split between the gateway/server and Python 
(based on application design and business logic constraints), and where can 
the errors pop-up?

If you are talking about custom CA certs, the two approaches I know of for 
this sort of stuff:

1- (Easy for developer, harder for client) The client application stuffs 
the certificate into a header.  Everything happens as normal Pyramid app.  
You just write pyramid code to require and validate the certificate 
header.  This isn't actually mTLS, but uses the client certificate similar 
to ssl keychains.

2. (Hard for developer, easy for client) Actually use TLS Mutual Auth, 
which is what Theron first brought up.  With mTLS, the client certificate 
is presented and validated during the TLS handshake - which means you would 
need to configure the gateway or mod_wsgi to handle the validation.

The large complexity of #2 is that many web servers / gateways can only be 
configured with a single client CA or a static client CA store - so 
building this as scalable to multiple clients may not necessarily be 
possible.

The three workarounds I can think of are:
1- Don't terminate TLS or validate the client certificate on the gateway, 
instead pass it all back to a python server like Waitress and see if you 
can handle everything via middleware to process the SSL connection.

2- Terminate TLS on OpenResty(nginx) and use a Lua script to handle the 
client validation.  Then you can proxy that back to mod_wsgi.  I 
opensourced our dynamic SSL certificate tool for OpenResty here - 
https://github.com/aptise/lua-resty-peter_sslers - it does not do client 
certificates, but IMHO is a good reference for what you want to 
accomplish.it looks like OpenResty has some builtin stuff for this, but 
if not - those are the correct hooks.  

3- Terminate TLS on the gateway but make it very lax for the client 
certificate to pass - basically just checking to see if the certificate is 
valid and from the CA.  Then validate the client a second time in 
middleware/tween to ensure the certificate is active and allowed.  


On Wednesday, November 15, 2023 at 9:13:39 AM UTC-5 Thierry Florac wrote:

> Hi,
> My problem is probably quite simple: I would like to be able, in a Pyramid 
> application, to create a custom security policy which could use an SSL 
> client certificate as a request credential to handle authentication 
> (authorized certificates being referenced in a database or stored in a 
> specific server directory).
> This application is then supposed to be published via mod_wsgi in an 
> Apache server located behind an HAProxy.
> I tried to search here and there but didn't find any information about 
> this...
> Any hint?
>
> Best regards,
> Thierry
> -- 
>   https://www.ulthar.net -- http://pyams.readthedocs.io
>

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pylons-discuss/39f47b19-0e08-4936-aaff-3da5822dc90fn%40googlegroups.com.

Re: [pylons-discuss] REF. FORMULARIOS E VALIDAÇÃO (PYRAMID)

[Laurent Daverio]

Hello,

Deform has a big problem, it generates widgets for Bootstrap 3. I had
patched mine it to make it compatible with Bootstrap 4, but now the
standard version is Bootstrap 5. And I've switched to React and Material UI
anyway. In retrospect, I think it's not a good idea to use a library which
binds validation and widgets.

As regards validation itself, I started with Colander, it was complicated
but worked. Then I used "schema" for a few months. Now I've seen the light
and I use Pydantic. I wonder why I used anything else in the past... Coming
from FastAPI, I believe you must be familiar with Pydantic.

In case you need frontend validation too, you can have a look at Yup, it"s
a bit like "schema", but for Javascript. Unfortunately, there is no
equivalent to Pydantic...

Laurent.

Le ven. 17 nov. 2023 à 16:13, Oberdan Santos  a
écrit :

> Olá!!   Gostaria de saber se todos têm adotado o DEFORM como biblioteca
> padrão para formulario e validação  ou outras bibliotecas de uso facil com
> o Pyramid ?
>
> Oberdan costa
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "pylons-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pylons-discuss+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/pylons-discuss/f86a52d6-171d-4097-b595-4e3718105d74n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pylons-discuss/CAB7cU6xPpeo_mUBjTC9obqZiRXcm40qhco%2Bk%2BnDSvCHmjn8eoQ%40mail.gmail.com.

[pylons-discuss] REF. FORMULARIOS E VALIDAÇÃO (PYRAMID)

[Oberdan Santos]

Olá!!   Gostaria de saber se todos têm adotado o DEFORM como biblioteca 
padrão para formulario e validação  ou outras bibliotecas de uso facil com 
o Pyramid ?

Oberdan costa


-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pylons-discuss/f86a52d6-171d-4097-b595-4e3718105d74n%40googlegroups.com.