N-Tier Application Authentication (RabbitMQ as Broker and C# as Business Tier) - WIF possible? -
i'm devoloping n-tier application c# business tier. it's kind of erp , need authentication (email/password) app. need permissions based on login (create orders, delete articles) informations should stored in 1 database.
as ui clients planned make wpf client, asp.net , maybe in future iphone/android. message broker use rabbitmq (clients talk business layer on amqp. due advanteges have more 1 business layer round robin dispatching).
on research authentication in n-tier applications found 1 advise windows identity foundation. wif completly new me. examples found handle asp.net applications.
my question is: wif right thing me or should implement session handling on own?
if wif can fit needs, best way handle this? have implement custom sts , place within wcf service?
as explicitly mentioning rabbitmq, suggesting servicestack service interface.
one issue mqs in general decoupled meta information, such http headers, inject authentication. should in contrast provide property session
(with pre authentication) or username
, password
in message (where later 1 not prefered, credentials passed in plain). sample solution built-in sessionfeature
of servicestack available in documentation.
another nice feature of servicestack can decorate handlers not authenticateattribute
requiredroleattribute
, requiredpermissionattribute
.
also: how plan queue message android? can expose internal mq outside, , there client available eg android? therefore suggest dual endpoint on http queue messages in whatever mq choose use. more information on how integrate mq in http service available in documentation.
with servicestack can spin many consumer instances want, there is plain communication without serivce stuff available.
trivia: authoring upcoming book on mastering servicestack little bit biased. nevertheless cover of questions in book, , provide code examples: bits , pieces scenario are covered here (do not frightened specific mq, interchangeable).
Comments
Post a Comment