Hi Bahaa,
I cc'd you directly because all discussion now takes place on the SF
lists.
Thanks for the follow up. This is the same architecture I have been
working on, however there is no examples on how to hook up to the
workflow or add new function that do crypto operations in the server
API. To go from the SOAP function to the OpenXPKI::Client I need to
know
what each function in the serverAPI is looking for as far as
parameters
and data structures and this seems to be missing in the docs.
Yes, these functions are still missing from the server. This is what
I will start to implement now.
Do you really need to know exactly which functions will be available
via the API *now*? I would suggest you start with implementing the
framework, write a SOAP server that connects to the server, handles a
login and runs the (implemented) nop() function.
Please also try to write tests in the t/ directory if possible (don't
know if you need a web server deployment for the tests).
Can we start by adding more commands to the
OpenXPKI::Service::Default::Command
We need to add a command that writes to the database like add a CA
cert
First things first. Let us start with
- CA certificate retrieval methods and
- a simple certificate request workflow
Why would you want to *write* a CA cert via a user interface?
BTW, there will be no direct write access methods to the database at
all. Everything that modifies the internal state will be wrapped in a
workflow (unless we have a very good reason not to).
cu
Martin
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
OpenCA-Devel mailing list
OpenCA-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openca-devel
