ipsilon.git/ipsilon/util, branch provsess

Add helper to store provider specific data

2015-01-26T21:57:35+00:00

Signed-off-by: Simo Sorce

Add source code context information to debug logs

2015-01-26T19:01:03+00:00

The log.debug() function helpfully adds the name of the function
invoking it but in a complicated software package there are many
functions/methods which share the same name. Thus a debug message
like this:

DEBUG(__init__): xxx

does not give you much context, there are probably hundreds of
__init__ methods. It would help to qualify the method name which it's
class name, that gives a lot more context when reading the
log. Sometimes it's also helpful to know the file and line number.

This patch adds the class name to the function and included the
filename and line number as well. The file path is trimmed to the last
3 components, sufficient to give context but not too verbose. Now the
debug message might look like this instead:

DEBUG(ipsilon/providers/common.py:129 LoadProviders.__init__()): xxx

Also included is a config option 'stacktrace_on_error' which will
include a stacktrace when the log.error function is called. It can be
very useful to see a stacktrace when logging an error, it defaults to
off.

Signed-off-by: John Dennis 
Reviewed-by: Simo Sorce

Add request/response logging via cherrypy tool hooks

2015-01-26T18:34:06+00:00

The ability to easily review the HTTP Ipsilon request and response is
boon for development and issue debugging. Normally these HTTP
conversations occur on SSL/TLS encrypted connections making it
difficult to use other tools to view the traffic. Client side tools
have known pitfalls (e.g. Firebug) and not all conversations are
browser initiated (e.g. SAML ECP). Logging performed by the server
hosting Ipsilon makes logging at the server level server specific
(e.g. Apache's dumpio requires post-processing the log file to extract
and reassamble the HTTP conversation). The best place to log requests
and responses is within Ipsilon using the cherrypy framework
Ipsilon is embedded in. Cherrypy provides user defined hooks that can
be invoked at specific places in the request pipeline. We establish a
hook at the last stage just before the response is written to the
client, it logs the incoming request and outgoing response.

Resolves: https://fedorahosted.org/ipsilon/ticket/44

Signed-off-by: John Dennis 
Reviewed-by: Simo Sorce

Use referer too as source of transaction IDs

2015-01-16T09:33:22+00:00

This allows us to use apache module that use things like ErrorDocument
directives to do internal redirects and still retain the original
transaction intact.

Signed-off-by: Simo Sorce 
Reviewed-by: Patrick Uiterwijk

Fix file permissions and remove shebang's

2014-12-16T15:51:43+00:00

Signed-off-by: Patrick Uiterwijk 
Reviewed-by: Simo Sorce

Add defaults to List objects

2014-12-05T20:44:06+00:00

Otherwise we get backtraces when checking for list members and no configuration
have been stored in the database yet.

Signed-off-by: Simo Sorce 
Reviewed-by: Patrick Uiterwijk

Allow to pass drectly a URL to the Store class

2014-12-05T19:49:30+00:00

This is useful for plugins that want to use their own database configuration
but still want to reuse he Store class for simplicity.

Signed-off-by: Simo Sorce 
Reviewed-by: Patrick Uiterwijk

Return proper errors if config is read-only

2014-11-12T22:47:39+00:00

Do not throw 501 errors, instead return warnings that the configuration
changes cannot be applied.

Signed-off-by: Simo Sorce 
Reviewed-by: Patrick Uiterwijk

Add option to source configuration from a file

2014-11-12T22:47:36+00:00

If the configfile:// schema is used, the data is sourced from an ini
style config file instead of being read from a database.

The tables in this data source will be considered read-only and
all modification functions will throw exceptions.

Only 2 and 3 columns tables are supported, and the first column
values must not contain spaces (typically a name/identifier).

The adminconfig db is the only supported one at this time.

Signed-off-by: Simo Sorce 
Reviewed-by: Patrick Uiterwijk

Remove unused option

2014-11-12T22:47:34+00:00

Autotable is always enabled, so remove the option and just alays use it.

Signed-off-by: Simo Sorce 
Reviewed-by: Patrick Uiterwijk