ppk

ppk
 
 

aaf1 ppk
aaf2 (idp-pp)

* Code tour
* Tester resources
* Invitation Client
* Query Syntax 
* Access Restrictions Discussion
* Modifying a wsdl file

latest news

Current version:  version name / stage (alpha beta ..etc) and  status (maybe?) s

Features:

• Search for a user in a whole federation, for approximate or exact matches.
• Search is secured: data encrypted,enforced shibboleth release .
• Search results are incrementally returned.
• Search progress is indicated as search proceeds.

Architecture:People Picker is implemented in 3 parts

• idp-pp: an idp component that exposes user search as a web-service
• fed-pp: a federated white pages component that search on all idp-pps. It will then return the list of results.
• clients: the programs (either web sites or applications) that users of the search functionality actually use. These pass the requests on to fed-pp to do all the hard work. 

Information flow:It is useful to see how information flows within people picker

1. the user types a query into a pp client
2. The client sends the query to fed-pp
3. fed-pp sends the query to each idp-pp
4. each idp-pp responds with results
5. when all results are back fed-pp responds to pp client (actually, people picker allows intermediate results and progress to be displayed as well).
6. pp client then displays results for the user

 
Technical background: With what other software/machines it interacts?
How?

What are its configuration files?

-        location

-        content

-        explanations (what is modified or what to look for)

-        log files if they exist, their location and what they track. 

chat online
email

General

• user guide
• screenshots 
• ppt
• Q&A

Technical

•  installation guide
• Configuration

Conception:

• functional requirements
•  technical requirements
• specification

Projects meeting:

• minutes
• planned meeting