kanidm VS pest

Check this: https://github.com/kanidm/kanidm/ Maybe not production ready, but looks very promising

Kanidm is a identity management platform with a ldap compatible interface, sso and more. It's still young, but the author works on the 389 ldap server at suse, so knows how to build a secure ldap alternative :)

Here is the OAuth/OIDC issue: https://github.com/kanidm/kanidm/issues/278

They are talking here: https://github.com/kanidm/kanidm/pull/485 about being an IdP with support for OIDC, so once that is implemented you could probably federate to Keycloak (or any other compliant IdP).

Might be worth filing an issue, I'm sure they'd love the feedback.

Kanidm: A simple, secure and fast identity management platform\ (22 comments)

Kanidm, it might not sound as fun or exciting but this sound engineering driven by exceptional people. Similarly, concread.

saml-rs, creating a SAML IdP in rust, kind of spun out of trying to do it for Kanidm.

And now they employ one of the lead 389 Directory Server developers (now the default in SUSE instead of OpenLDAP which is is still available but is going to be depreciated). The same person is also the lead developer of Kandim, a new beta IDM that looks really promising (but is likely quite some time from being ready for enterprise production).

And some related parser tools: - https://github.com/kevinmehall/rust-peg - https://github.com/pest-parser/pest - https://github.com/lalrpop/lalrpop

I had recently completed the first year of my Computer Science class at school and will begin my second year soon. My schools' class forces the use of Java programming language, and I absolutely hated it. So, over the course of a little less than a month, I wrote my own programming language, in Rust (objectively best programming language), using pest, to be as similar to Rust as possible, but compiling to Java.

I second pest.rs. Using it is fairly intuitive and there's also a live playground on their website which is great for quickly developing and testing your AST (abstract syntax tree) parser for whatever language you're implementing.

This is where you'll run into trouble. People who write parsing-related Rust crates generally write things like pest that expect their syntax to be defined completely at compile time so the parser can be run through the compiler's optimizers for best performance.

Give https://pest.rs a try.

For now I have used pest to generate an AST that borrows from the given input. But if I can manage to make the parser generic over the return type it may be worth a refactoring.