We have an internal app here that we would like to integrate with
FlexWiki. The idea is that we would have a IE control in the .Net app
that shows a custom view of some wiki pages. The implementation for this
is pretty straightforward, but we recently hit upon a snag: our internal
app has its own security model.

The issue is that certain pieces of data in the app are marked private,
and can only be viewed by a set of users (defined per-item). We would
like to be able to add the capability for FlexWiki to check our app's
security database to restrict access to the corresponding wiki pages.

I'm curious what the feasibility of this would be? Ideally, we would
like to use the built-in security provider for most of the pages, but on
a per-page basis layer on top of it the means to secure a page using a
user/role list that comes from our app's database. Roughly, I am
thinking of something where the wiki looks for a property named
something like _CustomSecurityProvider that understands how to check the
internal database first and then fallback to the wiki provided security
if nothing was specified.

Being an internal app, we can assume that the usernames will match (we
are using Active Directory for wiki auth, and can assume that the
internal app will use the same names).

Does this sound feasible? Any other issues that might come up?

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Flexwiki-users mailing list
Flexwiki-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flexwiki-users

Reply via email to