1
1

Looking at this: http://meta.osqa.net/questions/1208/how-would-i-go-about-setting-up-a-private-qa-instance and the Jira referenced by it...

For a quick solution to this, how hard would it be to set it up so there was a text file or something that listed allowed openid URLs? In that case, only two changes would be required:

1) No anonymous access to the site at all. Anonymous access is redirected to openid login page.

2) Part of the authorization process checks the openid url with the access list, if it doesn't match, it kicks to some not authorized page.

Administrators would just manage that text file on the server. I know a nice admin page would be nicer, but I'm just thinking of a solution that maybe could be implemented very easily.

asked 24 Jul '10, 01:40

taotree's gravatar image

taotree
16122
accept rate: 0%

Upon further understanding of some things, it seems likely that the ACL would be a list of emails instead of URLs which would probably be easier to manage anyway.

(24 Jul '10, 11:18) taotree
Be the first one to answer this question!
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×32
×7

Asked: 24 Jul '10, 01:40

Seen: 1,051 times

Last updated: 24 Jul '10, 11:18

powered by OSQA