federico.caselli ha scritto:
Ma con reporting services funziona, anche senza dominio...
In tutta franchezza, non è che conosca benissimo i Reporting Services.
Stando alla logica, però, la questione è perfettamente analoga.
Ora, non ho ben capito come passi le credenziali al servizio, ma sembra davvero strano che questo accetti richieste da un account locale di un client che, oltretutto, non fa parte di un dominio.
Mi sono comunque documentato e ho trovato il seguente link (benedetta technet!
):
Configuring Authentication for Reporting ServicesNello specifico:
By default, the report server and Report Manager virtual directories are configured to use Integrated Windows authentication. Anonymous access is not enabled on the virtual directory. No other authentication methods are selected.
If you are using default security, each user who requires access to a report server must have a valid Windows user account or be a member of a Windows group account. You can include accounts from other domains as long as those domains are trusted. The accounts must have access to the Web server hosting the report server, and must be subsequently assigned to roles in order to gain access to specific report server operations.
The default settings work best if all client and server computers are in the same domain or in a trusted domain, the browser type supports Integrated Windows authentication, and the report server is deployed for intranet access behind a corporate firewall. If you support Internet access to a report server or if you are using Workgroup security, you will most likely need to customize the default settings.
Trusted and single domains are a requirement for passing Windows credentials. Credentials can be passed more than once only if you enable Kerberos version 5 protocol for your servers. If Kerberos is not enabled, credentials can be passed only once before they expire.Potresti quindi mostrare come effettui il passaggio delle credenziali?
