Ok, I'll do that. BTW. As I'm doing a bit of research how providers support Attribute- Exchange, it seems their behaviour and supported schemas can be quite different (for example, Google ignores optional attributes). So the function might need a parameter from which the openid provider can be determined, to allow customizations for well-known providers.
Erkki L On Feb 6, 9:54 am, Jeppe Nejsum Madsen <[email protected]> wrote: > Erkki Lindpere <[email protected]> writes: > > Thanks! > > > I'm now trying to customize the attribute-exchange and noticed that it > > is embedded in a longish method. I think it would be good if this was > > extracted to a method (maybe: def reqAttributeExchange: > > Option[FetchRequest] ?) so that ax info could be modified without > > digging into the rest of the logic or copy'n'pasting. Specifically, I > > think these lines could be extracted: > > > // Attribute Exchange example: fetching the 'email' attribute > > val fetch = FetchRequest.createFetchRequest() > > fetch.addAttribute("email", > > // attribute alias > > "http://schema.openid.net/contact/email";, // > > type URI > > true); // > > required > > I maybe about to look at the openid stuff for a project and will need > this functionality as well :-) If you could open a ticket on Assembla > (when it's availability has been announced) I'll have a look... > > /Jeppe -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
