ImageVerifierCode 换一换
格式:PPT , 页数:13 ,大小:118KB ,
资源ID:376587      下载积分:2000 积分
快捷下载
登录下载
邮箱/手机:
温馨提示:
如需开发票,请勿充值!快捷下载时,用户名和密码都是您填写的邮箱或者手机号,方便查询和重复下载(系统自动生成)。
如填写123,账号就是123,密码也是123。
特别说明:
请自助下载,系统不会自动发送文件的哦; 如果您已付费,想二次下载,请登录后访问:我的下载记录
支付方式: 支付宝扫码支付 微信扫码支付   
注意:如需开发票,请勿充值!
验证码:   换一换

加入VIP,免费下载
 

温馨提示:由于个人手机设置不同,如果发现不能下载,请复制以下地址【http://www.mydoc123.com/d-376587.html】到电脑端继续下载(重复下载不扣费)。

已注册用户请登录:
账号:
密码:
验证码:   换一换
  忘记密码?
三方登录: 微信登录  

下载须知

1: 本站所有资源如无特殊说明,都需要本地电脑安装OFFICE2007和PDF阅读器。
2: 试题试卷类文档,如果标题没有明确说明有答案则都视为没有答案,请知晓。
3: 文件的所有权益归上传用户所有。
4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
5. 本站仅提供交流平台,并不能对任何下载内容负责。
6. 下载文件中如有侵权或不适当内容,请与我们联系,我们立即纠正。
7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。

版权提示 | 免责声明

本文(Internet2 WebISO Project.ppt)为本站会员(tireattitude366)主动上传,麦多课文库仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对上载内容本身不做任何修改或编辑。 若此文所含内容侵犯了您的版权或隐私,请立即通知麦多课文库(发送邮件至master@mydoc123.com或直接QQ联系客服),我们立即给予删除!

Internet2 WebISO Project.ppt

1、Internet2 WebISO Project,RL “Bob“ Morgan, University of Washington,Topics,How it came to be Project status WebISO defined Project goals Architecture/Interface,How it came to be,Shibboleth project assumption: every campus has intra-campus web authentication startling discovery: not true The MACE way:

2、 do something about it brief search for likely sharable implementations U of Washingtons “pubcookie“ chosen as starting point project started to make “appropriate progress“ now looking at architectural issues,WebISO project status,Its live: web: http:/middleware.internet2.edu/webiso/ email: mace-web

3、isointernet2.edu, 40 on list phone calls: bi-weekly, 3:30PM ET Tuesdays active work on refining project goals Pubcookie distribution 10 sites with code, 1 non-UW deployment (CMU), a few pending; BSD-style license CMU-contributed changes being incorporated freely-available distribution posted shortly

4、WebISO defined,Organizational web-based sign-on system Typically includes: single sign-on (only “type something“ once to access multiple targets) use of standard authentication backend (LDAP, Kerberos, NIS, NT, etc) keep passwords away from application web servers (have them only entered into “webl

5、ogin“ server) “Most reinvented technology of the 90s“,WebISO components,Module for application webservers check for authentication info on request, if not found redirect browser to weblogin server interpret authentication info, pass to web application Weblogin server accept redirected request, promp

6、t for userid/password (or other authn method) return browser to target webserver, with authn info Message format for appserver weblogin,The pubcookie story,“Just another webiso“ written in C Apache, MS-IIS target web servers Apache-based weblogin Kerberos 5 backend built-in, others possible in produ

7、ction since 1999 web-based documentation signed/encrypted messages, sent using cookies works with almost all browsers,Pubcookie planned improvements,better docs, clearer installation procedures more authentication backends, pluggable X.509 client cert authn, Kerberos client authn variable-length SSO

8、 session support per-user, per-server settings “blinded“ userids easier/automatic key management authn tokens in URLs (cross-DNS-domains) robustness, quality assurance, modularity . many require rethinking, justification, threat model,Project goals,Not just pubcookie enhancement/support Work with pa

9、rtner projects to ensure meeting requirements: uPortal (http:/mis105.mis.udel.edu/ja-sig/uportal/) Open Knowledge Initiative (http:/mit.edu/oki) Shibboleth Define architecture and interface to which multiple webiso implementations can conform,WebISO architecture + interface,Application interface man

10、y issues similar to Shibboleth target arch webisos typically supply plain old userid what about authorization data? what about privacy protection? forced/step-up authentication app specifying authn method (pubcookie supports both Kerberos and SecurID) app selectively turning off SSO session manageme

11、nt e.g., “single sign-off“ from all apps at once,Webiso design centers,Webiso implementations differ in approach support for admin apps: high security/control support for student-run apps: simplicity, ease of install/support assume local software on client (eg Kerb plugin) cross-DNS-domain support r

12、equired assume underlying authn infra (Kerb, X.509) support home-grown apps, package apps, static pages Can one package do it all?,Application interface 2,The 3-tier problem (aka delegation) seen by many app servers that need to access backend services (eg IMAP) on behalf of user seen by all portals

13、 that act as intermediaries many sites implement “practical“ solutions can webiso provide a standard approach? will any solution be dependent on underlying delegation technology, eg Kerberos or X.509? is this a WebISO project problem?,Conclusion,WebISO project up and running Pubcookie code available Architecture/interface issues engaged Sites still reinventing, so need is there Partner projects need support http:/middleware.internet2.edu/webiso/,

copyright@ 2008-2019 麦多课文库(www.mydoc123.com)网站版权所有
备案/许可证编号:苏ICP备17064731号-1