HTTP Post身份验证 [英] HTTP Post Authentication

问题描述

寻找关于认证方案的一些一般设计建议

用于B2B事务入站，通过HTTP Post Listener ASPX页面读取来自请求正文的二进制流的
。我想在

处理帖子内容之前添加一个

身份验证过程来验证传入的事务。虽然在

帖子内容中添加用户名和密码是可行的，但它是最后的解决方案之一，因为它会让很多客户重新格式化他们的消息。 br />

我想到的一些设计思路是为

商店用户名和pswd添加自定义请求标题。


请建议。

Looking for some general design recommendations on an authentication scheme
for B2B transactions inbound via an HTTP Post Listener ASPX page that reads
the binary stream from the request body. I would like to add an
authentication process that validates the incoming transaction prior to
processing the post content. Although adding username and password to the
post content is feasable, it is one of the last solutions since it will
involve many customer''s to reformat their messages.

Some design ideas that I have in mind are adding a custom request header to
store username and pswd.

Recommendations please.

推荐答案

您应该查看基本身份验证。


-Brock
DevelopMentor
http://staff.develop.com/ballen

You should look into Basic Authentication then.

-Brock
DevelopMentor
http://staff.develop.com/ballen

通过HTTP Post Listener ASPX页面查找有关B2B事务入站的身份验证方案的一般设计建议，该页面从中读取二进制流请求机构。我希望在处理帖子内容之前添加一个验证进程验证传入的
事务的验证过程。虽然在帖子内容中添加用户名和密码是可行的，但它是最后一个解决方案之一，因为它将涉及许多客户重新格式化他们的消息。
<我想到的一些设计思路是添加一个自定义请求
标题来存储用户名和pswd。

建议请。

Looking for some general design recommendations on an authentication
scheme for B2B transactions inbound via an HTTP Post Listener ASPX
page that reads the binary stream from the request body. I would like
to add an authentication process that validates the incoming
transaction prior to processing the post content. Although adding
username and password to the post content is feasable, it is one of
the last solutions since it will involve many customer''s to reformat
their messages.

Some design ideas that I have in mind are adding a custom request
header to store username and pswd.

Recommendations please.

这是一个链接到非常好的Web身份验证主题资源...不是

我认为你确切的，但它可能会有所帮助：
http ：//msdn.microsoft.com/library/de...cnetlpmsdn.asp

" Chris Fink" <章******* @ discussions.microsoft.com>在消息中写道

新闻：D9 ********************************** @ microsof t.com ...

Here is a link to very good resource for web authentication topics...not
your exact one I think, but it might help :
http://msdn.microsoft.com/library/de...cnetlpmsdn.asp
"Chris Fink" <Ch*******@discussions.microsoft.com> wrote in message
news:D9**********************************@microsof t.com...

通过HTTP Post Listener ASPX页面寻找关于B2B事务入站的认证
方案的一般设计建议
读取
来自请求正文的二进制流。我想添加一个
身份验证过程，在处理帖子内容之前验证传入的事务。虽然在
帖子内容中添加用户名和密码是可行的，但它是最后的解决方案之一，因为它将涉及许多客户重新格式化他们的消息。

一些我想到的设计思路是添加一个自定义请求标题
来存储用户名和pswd。

建议请。

Looking for some general design recommendations on an authentication
scheme
for B2B transactions inbound via an HTTP Post Listener ASPX page that
reads
the binary stream from the request body. I would like to add an
authentication process that validates the incoming transaction prior to
processing the post content. Although adding username and password to the
post content is feasable, it is one of the last solutions since it will
involve many customer''s to reformat their messages.

Some design ideas that I have in mind are adding a custom request header
to
store username and pswd.

Recommendations please.

你能详细说明一下基本的认证设计吗？


我认为它会涉及设置Request Header的授权标签和

然后将用户名和密码用冒号分隔，然后在响应中阅读

授权标签并妥善处理。


唯一的问题是我无法设置请求标题授权，因为它只是

只读。


任何想法都是？


Brock Allen写道：

Can you elaborate more on the basic authentication design?

I assume it would involve setting the Request Header''s authorization tag and
then placing the username and password seperated by a colon, and then reading
the authorization tag in the reponse and handling it appropriately.

Only issue is that I cannot set the Request Header authorization since it is
read only.

Any ideas''s?

"Brock Allen" wrote:

然后你应该查看基本认证。

-Brock
DevelopMentor
http://staff.develop.com/ballen

You should look into Basic Authentication then.

-Brock
DevelopMentor
http://staff.develop.com/ballen

寻找一般通过HTTP Post Listener ASPX页面设计有关B2B事务的身份验证方案的建议，该页面从请求正文中读取二进制流。我希望在处理帖子内容之前添加一个验证进程验证传入的
事务的验证过程。虽然在帖子内容中添加用户名和密码是可行的，但它是最后一个解决方案之一，因为它将涉及许多客户重新格式化他们的消息。
<我想到的一些设计思路是添加一个自定义请求
标题来存储用户名和pswd。

建议请。

Looking for some general design recommendations on an authentication
scheme for B2B transactions inbound via an HTTP Post Listener ASPX
page that reads the binary stream from the request body. I would like
to add an authentication process that validates the incoming
transaction prior to processing the post content. Although adding
username and password to the post content is feasable, it is one of
the last solutions since it will involve many customer''s to reformat
their messages.

Some design ideas that I have in mind are adding a custom request
header to store username and pswd.

Recommendations please.

这篇关于HTTP Post身份验证的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！