You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 7, 2020. It is now read-only.
Portia fails to verify credentials due to the fact that portia does not parse the -d parameter, instead uses the default WORKGROUP.
I make a temporary validation check on line: 2342 by printing my inputs (username, password, domain).
Editing the portia.py file and manually specifying the domain value it seems to work only for account verifying function and next keep using the WORKGOUP value for the rest of the code.
I have identified also on lines number 2720 and 2730 domain value is assigned with the value WORKGROUP instead taking the user's input.
Maybe domain="WORKGROUP" parameters exists also in multiple lines on .py file.
The text was updated successfully, but these errors were encountered:
wizard32
changed the title
Domain is not set [WORKGROUP by default]
Domain are not set [WORKGROUP by default]
Nov 17, 2017
No real resolution yet. I avoided by copying the portia.py and renaming it to the target domain. then edit the file and replace WORKGROUP with the domain of the target. There are other problems, but it cures that one....
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Portia fails to verify credentials due to the fact that portia does not parse the -d parameter, instead uses the default WORKGROUP.
I make a temporary validation check on line: 2342 by printing my inputs (username, password, domain).
Editing the portia.py file and manually specifying the domain value it seems to work only for account verifying function and next keep using the WORKGOUP value for the rest of the code.
I have identified also on lines number 2720 and 2730 domain value is assigned with the value WORKGROUP instead taking the user's input.
Maybe domain="WORKGROUP" parameters exists also in multiple lines on .py file.
The text was updated successfully, but these errors were encountered: